Season control

Load the holder CSV, review, then permanently lock eligibility before opening. MCQ balances and continuous-holding rules still apply during the season.

Columns: wallet,mcq_balance,quotron_count. MCQ amounts use readable units without commas.

No list loaded.

Connect the economic admin after deployment to view current settings.

Change a price

Paid-play allocation

QTR-0121 · Deployment pending.

Paid-play MCQ allocations, Chance and redemption ETH are reserved here. Buy MCQ in batches, then claim reflections and burn when ready.

Loading treasury balances…

Configure the collection default and each Builder property. Royalties are independent of gameplay.

Royalty terms have not been configured.

Add prize tokens before or during the season. Existing Chance reservations stay unchanged.

Funding from the ETH reserve is manual: withdraw the ETH, buy the prize token, then top up here. No automatic swap.

Deposit ETH, tokens or NFTs into the jackpot, or fund reward reserves. Your wallet confirms each transfer.

Builder bonus: one NFT in addition to the $20 and trophy. Enable and load six NFTs from one collection before launch. Assigned in deposit order. ERC-721 loading uses two confirmations: transfer, then register. To finish an interrupted registration, enter the same collection and token ID manually.

Not configured

Deployment pending.

All unanswered plays

Deployment pending.

Retry the original Pyth result. No new play, reroll or additional game fee. Game requests reject new results at or after three days. Only unanswered requests can then be cancelled without refund; results recorded before the deadline can settle later. Jackpot requests reject results at or after their 96-hour deadline; use fixed-wallet rollover instead of retrying late randomness.

Deployment pending.

Loading the confirmed season schedule…

The standard schedule is set from launch: CEO claims open after 9 days, and the season ends after 14 days. No dates need to be entered here. After season end, settle outstanding plays before recording the jackpot snapshot block.

Earned prizes stay reserved. Unused reward reserves unlock after the season ends and all plays settle. Jackpot withdrawals require a locked empty snapshot and no eligible weight.

Uses the recorded closing block after every accepted play has settled or reached the three-day cancellation rule. Wait for that block to finalize. Unclaimed escrow pieces are excluded.

The contract verifies historical ownership and weight. Anyone can submit holders; only historical onchain weight is counted. The first Pyth request must succeed strictly before 96 hours after the verified snapshot completes. If no request succeeds, fixed-wallet rollover becomes available then. A successful request has its own 96-hour result deadline: callbacks at or after it are rejected even before rollover. A result recorded in time may resolve later. Failed requests do not restart clocks; there is no repeat draw. Rollover delivery may need retries; the manual draw tool verifies the fixed drand round cryptographically, and the receiver pays the selected winner manually. The snapshot hash is informational, may be zero, and does not determine eligibility.

No winner selected.

Failed payouts stay reserved for the same winner. No rerolls.

Use this only for an ERC-721 sent directly to the reward vault that was never registered. Registered, reserved and awarded prizes cannot be withdrawn here. The reward-vault owner must confirm the return.

Custody and prize reservations are checked before review and again before sending.