every burn · one row per sweep · checked against the chain
burned to the dEaD address
measuring
reading the chain — keyless eth_call
nothing has burned yet — the first sweep writes the first row; a zero here is the honest state, not a placeholder
burn-pending accrual
measuring
reading the chain — keyless eth_call
nothing accrued right now — the lane credits at the next vault-lane harvest
harvest cycles
measuring
reading the chain — keyless eth_getLogs
no harvest yet — the first one is pending
sweeps skipped
measuring
reading the chain — keyless eth_getLogs
the tape
| block | transaction | amount | source token | label |
|---|
no sweeps on the tape yet — the first burn writes the first row; the file is the same one you can diff
The file behind this table is data/burn_tape.json — plain data, rebuilt by an operator tool, never generated in your browser. The live figures above come straight off the chain, so the page never waits on a file to be honest.
the lane
Vault-lane revenue splits by named constants — DEPOSITOR_BPS = 9000 and BURN_BPS = 1000 in src/RoamVault.sol: nine parts in ten raise depositors' share price, one part in ten is the burn cut. The dev take on this path is structurally zero — nothing is retained anywhere.
The burn cut accumulates as accounted accrual on the roamer — conserved, never treasury, never junk-forwarded. sweepToBurn() is permissionless and nonReentrant (src/RoamingHarvester.sol): it swaps the accrual to WELL through the pinned router and transfers the WELL to the dEaD address, emitting one Burned event per token. A token that cannot route is skipped and the rest of the tail stays live — SweepSkipped carries the reason. No operator signature is needed for a sweep: anyone can fire it, and the tape exists whether or not we pull it.
Contracts and tokens this page reads, all pinned once in site/js/config.js: roamer 0xC7a21Aa8C15C7032eE2e8352244a0f3D2154dC68 · vault 0xefA732aF74CaC318414BE8A1D645F3Ca5AB72E86 · WELL 0x5d08c35BcF268f4031BF3898e42b895Ff0779a24 · the burn address 0x000000000000000000000000000000000000dEaD.
agent identity — no identity held: the operator holds no token on the canonical ERC-8004 agent registry (0x8004A169FB4a3325136EB29fA0ceB6D2e539a432, the same address on every chain), probed once keylessly on 2026-10-06 against chain 4663. This page reports the protocol; it claims no agent identity.
Everything here is MIT — fork it, mirror it, and replay every figure on chain 4663.