Chain 2800 · read live, block by block

The Burn Engine

Every number on this page is read from the chain the moment you load it, straight from public RPC, with no API, no cache and no committee. If a number is zero, you see the zero.

connecting to rpc.aere.network…

Burned forever

AereFeeBurnVault is the protocol's burn endpoint: a sealed contract with no withdraw function, no admin, and no upgrade path. Value that enters never leaves. The counters below are lifetime totals kept by the contract itself.

AERE burned · all-time
…
totalBurnedAERE() · native AERE received by the vault, lifetime
Obliterated to 0x0
…
totalSentToZero() · swept on to the zero address, unreachable forever
Awaiting the next sweep
…
currentAEREBalance() · sits in the vault until anyone calls sweepToZero()
WAERE sealed in the vault
…
WAERE.balanceOf(burn vault) · wrapped AERE routed here by AereSink, locked permanently
WAERE at the dead address
…
WAERE.balanceOf(0x…dEaD) · community burns by convention

The router that nobody can touch

AereSink takes every protocol fee stream and splits it three ways. The split below is not copy: it is read live from the contract's immutable storage. There is no owner, no admin role, no pause switch, and no function to change these percentages. Changing them would require deploying a different contract.

…
…
…
Burn: straight to the burn vault Buyback & burn: non-AERE fees swapped to AERE, then burned Staker yield: drips to sAERE holders over 7 days
checking wiring…

Recent routing activity

scanning recent blocks…

Activity is scanned from the most recent blocks (about the last 40 minutes). The full event history is permanently available on the AereSink contract page.

Staker yield · sAERE

sAERE is the staking receipt vault. Fees routed to the staker bucket land here and vest linearly over 7 days, lifting the WAERE-per-sAERE exchange rate for every holder. No admin, no parameter setters: the drip is deterministic code. Do not deposit into it: this first vault is deprecated, with a known high-severity accounting defect (arrivals not yet synced are counted twice); the corrected vault, sAEREv2 (0x9B58…73a2), is deployed but nothing routes to it yet.

WAERE staked in the vault
…
totalAssets() · vested assets backing all sAERE shares
sAERE shares outstanding
…
totalSupply() · includes the permanent inflation-guard seed
Yield vesting right now
…
undistributedRewards() · arrived fees still dripping into the share price
Drip status
…
rewardRate() + periodFinish() · the 7-day linear vesting schedule

The standing bug bounty

AereBugBountyVault holds AERE committed to security researchers. Deposits are permanent: there is no general withdraw, and any single payout is capped to a fixed share of the pool, so no key compromise can drain it in one call.

Bounty pool balance
…
WAERE.balanceOf(bounty vault) · committed to disclosures, withdraw function does not exist

How it's wired

One path, no discretion. Protocol fee sources approve AereSink and call flush(). The sink splits the amount by its immutable percentages: the burn share goes to the burn vault, the buyback share is swapped to AERE and burned, and the staker share lands in sAERE where it vests linearly over 7 days. Anything anyone sends to the burn vault directly is burned too; the vault doesn't care who sends.

Contract addresses on this page are the canonical mainnet deployments: AereSink 0x6958…1676 · AereFeeBurnVault 0x696a…B2c6 · sAERE 0xA212…50b0 (deprecated, flawed: do not deposit) · WAERE 0x7e84…f5e8 · AereBugBountyVault 0x253f…9cD3. Read them yourself over RPC at rpc.aere.network; this page has no privileged data source.