Questions, answered.

Closest to it: a closest-to-target prediction lottery. The amount you bet IS your guess. The top 3 closest slots split 84% of the pot (73 / 7 / 4). Another 10% goes to seed-phase contributors. 5% rakes to $BURN. 1% pays whoever fires the settle button.

Because we're on Ethereum mainnet. Every claim is a real transaction with real validator settlement. The cheapest slot (0.001Ξ) plus gas is real money in absolute terms even when the slot itself is small. We don't hide this · we lean into it. Gas is the filter that keeps bots out. Read why →

If 24h passes during seed phase without crossing the 3Ξ threshold, every entry gets refunded. You lose gas, you get your ETH back.

Per-address cap of 50 slots forces sybil overhead. Cheap-slot carpet bomb requires 125+ ETH committed, 10+ funded wallets, gas across every claim, and irrational honest participation to be profitable. Monte Carlo here →

Ethereum future blockhash. At game creation, the contract records a reveal block far enough in the future to cover any reasonable game duration. When that block mines, its hash mod 1,000 gives the target slot. No oracle, no Chainlink, no manipulation surface.

After Ethereum's 256-block blockhash window (~50min), anyone can call reroll(roundId). New reveal block, new target, small bounty to whoever calls. The only way a round can't settle is if Ethereum itself halts.

Directly to the live $BURN contract at 0x886fab.... Plain ETH transfer, no bridge. Fills the buyback reservoir. The existing MEV-bot economy drains it into the permanent lock pile. BurnBomb is the primary deflation engine for $BURN.

10% of the FINAL pot is reserved for whoever contributed during the seed phase (before the 3Ξ threshold is hit). Your share is pro-rata to your seed contribution. The math rewards early movers asymmetrically. Worked examples →

No. The only owner function is emergencyResolveStuckRound, which only enables per-claimer refunds and has no recipient parameter. After BurnBomb #001 successfully settles, the owner calls freezeAdmin() and even that function is permanently disabled. All 8 guarantees →

No. The contract logic is immutable from deploy. No UUPS, no proxy, no upgrade authority. What's revocable is a thin admin layer (pause + emergency refund) that exists only for round #001 as a proof-of-life safety net. After #001 settles cleanly, the founder calls freezeAdmin() · a one-way function that permanently disables all three admin paths. From that block, the contract is fully autonomous forever.

Two paths. Normal: if 24h passes during seed phase without crossing the 3Ξ threshold, the round auto-enters refund state and every claimer can pull their ETH back immediately via refundMyClaim(). No waiting. Emergency: if a round is genuinely stuck due to some unrecoverable state, the owner can flip it to refund-eligible after a 90-day delay (this exists only as a safety net for the unforeseen). Even then, the owner cannot specify a recipient or drain funds. After freezeAdmin(), the 90-day emergency path is removed entirely · only the 24h auto-refund remains.

Since the contract is immutable, we can't patch in place. The recovery sequence: pause new claims, wait the 90-day emergency window if needed, return everyone's ETH via refundMyClaim(), and deploy a fresh v2 contract with the fix. BurnBomb #001 exists exactly so this situation is caught BEFORE we ship the freezeAdmin tx.

In the BurnBomb contract itself. Pull-payment pattern means nothing moves until settle() runs. Winners, 2nd, 3rd, and seed-dividend recipients all call withdraw() after settle to claim their share. The contract never auto-sends · you pull. No one can front-run you. No one can block you.

Two fixes. Rounding dust (a few wei lost in percentage math) is absorbed into the winner share · the contract computes winner as pot - allOtherSlices, so every wei leaves the contract during settle. Direct ETH sends are rejected by the contract's receive() function · anyone trying to send raw ETH outside of claim() gets reverted. Zero stranded funds.

One at a time for v1. The bracket reopens when the current round settles or refunds.

Design audit by Codex underway right now. Hardhat tests, mainnet fork tests, Etherscan/Sourcify verification all required before deploy. Status updates on the safety page.