Raid the Sanctum
This Sanctum's hot key is a public contract. Anyone can call it from their own wallet, pay their own gas and withdraw, the same way a thief with a stolen key would. You keep whatever the caps let out, which by design is very little.
01Leak meter
Leak meter
The caps let out 1% of the prize per hour and 2% per rolling 24 hours, with no queue. That outflow is the design working as intended. The meter reads Base live on every page load.
Not deployed yet
The bounty Sanctum gets 0.5 ETH at launch. Everything on this page turns on once its address is published.
withdraw(ETH, you, raidableNow). Simulated first; nothing is sent if it would revert.
- Prize in the Sanctum
- –
- Designed leak per day
- –
- Designed leak per hour
- –
- Rules on chain
- –
- Raids so far
- –
- ETH taken, all raids
- –
The daily cap is the hard limit. The hourly cap is a fixed window that starts at the first withdrawal, so up to 1.99% can leave in two transactions a few seconds apart across a window boundary. The rolling 24-hour cap still holds. Raids are first come, first served, and bots will compete for each hour's room.
02How to raid
How to raid
It takes one call on the key contract, with no sign-up or allowlist. If the balance ever leaves faster than the caps allow, the mechanism failed and the raider keeps it.
The call
On the bounty key contract, call:
withdraw(address token, address to, uint256 amount)- token
0x0000000000000000000000000000000000000000(ETH only)- to
- any address except the key contract and the Sanctum
- amount
- at most
raidableNow(), in wei
"over cap"The amount is above what the caps have left. Nothing is queued: the queue is off for this Sanctum."frozen"A guardian or the cold key froze it. Nothing leaves for 24 hours."amount"The amount is zero."eth only"The token is not ETH. Only ETH can be raided."to"The destination is the key contract or the Sanctum itself.
From a terminal, with Foundry
Read what you can take, then take it. --account you is your own Foundry keystore.
cast call BOUNTY_KEY "raidableNow()(uint256)" --rpc-url https://mainnet.base.orgcast send BOUNTY_KEY "withdraw(address,address,uint256)" 0x0000000000000000000000000000000000000000 YOUR_ADDRESS $(cast call BOUNTY_KEY "raidableNow()(uint256)" --rpc-url https://mainnet.base.org | cut -d' ' -f1) --rpc-url https://mainnet.base.org --account youBOUNTY_KEY is filled in with the live address once it is deployed.
| Rule | Value | Why |
|---|---|---|
| Caps | 1% per hour, 2% per rolling 24 h | A fifth of a normal Sanctum's caps, so the prize lasts. |
| Queue | Off | Anything above the caps reverts instead of queueing, so nobody can park a large transfer and force freezes. |
| Raids | ETH only, to an outside address | The leaderboard counts ETH raids to outside addresses only. First come, first served. |
| Guardians | Chosen by the admin | They can freeze the game for 24 hours at a time and renew the freeze; while it is frozen nobody can raid. Outside watchers can't freeze it. |
| Cold key | BountyCold, a locker contract | Its owner can only freeze, unfreeze and choose guardians, and can renew a freeze indefinitely. It has no way to withdraw the prize, change the rules or replace the public key. The prize leaves only through raids. |
| Guardian recovery | Off, for good | BountyCold switches recovery off in the same transaction that creates the game, and has no way to switch it back on. Guardians can never vote in a new cold key, so the locker stays the cold key forever. |
| Prize top-ups | 10% of FeeRouter inflow | Seeded with 0.5 ETH at launch, then fed by fees, into the same locked Sanctum. |
03Leaderboard
Leaderboard
Every raid emits an Attempt event. An indexer reads them from Base every few minutes and builds this table.
No leaderboard yet
The leaderboard appears once the bounty Sanctum is live and the indexer has run.
| # | Raider | ETH taken | Raids | Last raid |
|---|