Rules

This market will resolve to “Yes” if the countdown timer associated with the contract at address 0xf732427438e7847040623650fe24335f03e2aac0 on Robinhood Chain reaches zero at any time after the creation of this market and strictly before August 31, 2026 at 23:59:59 UTC.

The timer’s expiry timestamp will be calculated using the contract’s public lastBuyAt() value as follows:

timerExpiry = lastBuyAt + 14,400

where lastBuyAt is a Unix timestamp in seconds and 14,400 seconds equals four hours.

Accordingly, this market will resolve to “Yes” if it can be verified on-chain that, following the creation of this market, the active value of lastBuyAt resulted in a timerExpiry strictly earlier than the cutoff Unix timestamp:

1788220799

Otherwise, this market will resolve to “No.”

For the purposes of this market:

• Each qualifying buy may update lastBuyAt and therefore reset the timer’s expiry to four hours after that buy. The timer will only be considered to have reached zero once four uninterrupted hours have elapsed after the most recent qualifying buy.

• If another qualifying buy updates lastBuyAt before the previously calculated timer expiry, the earlier expiry does not count because the timer did not reach zero.

• A timer expiry exactly equal to 1788220799 does not qualify. The calculated expiry must be strictly less than 1788220799.

• If the timer had already reached zero before this market was created, that prior expiry does not count. Only a timer expiry occurring after market creation is eligible.

• The determination must be based on verifiable on-chain state, transaction logs, block timestamps, public block explorers, or node RPC queries for Robinhood Chain.

• Historical contract state or transaction logs may be used to determine the applicable lastBuyAt value and verify that no subsequent qualifying buy reset the timer before its calculated expiry.

• If the relevant on-chain state is permanently unavailable or ambiguous, the outcome will be determined by consensus among credible block explorers, archival RPC providers, and other reliable on-chain records.