— IMD burned across Base, Ethereum and Robinhood Chain. Of the Base burns, — were burned natively on Base and — came over from Ethereum through the BurnExecutor. Supply is down — from the 10M start.
Snapshot — · read from each chain's public RPC
Total IMD burned so far, at the end of each day since the Base token launched on Aug 31, 2023.
Last 30 days: — IMD burned, — vs. the 30 days before (—).
IMD burned in each calendar month, split the same way. The current month is partial.
BurnExecutor amounts are dated by their Ethereum bridge transaction; the burn on Base can land up to a day later, so the native line dips by up to ~1,700 IMD on two days. Base is sampled at midnight UTC each day; Ethereum and Robinhood are summed from every transfer into their burn wallets.
The BurnExecutor on Ethereum collects IMD, bridges it to a burn receiver on Base (0xf9d7…6793) and the receiver burns everything it holds. Everything else burned on Base counts as native.
Not burned yet: — IMD waiting in the two BurnExecutors on Ethereum for the next bridge, and — IMD sitting in the old Base receiver (0x4b11…EaDA), whose burn call doesn't match the token, so it can't be burned.
Running total of IMD bridged from Ethereum to the Base burn receiver, by day.
Wallets that sign the Ethereum transactions sending the BurnExecutor's IMD to Base, where it is burned. On the current executor anyone can do this; the caller pays the LayerZero fee and gas.
— burnkeepers have triggered — bridges, sending — IMD to burn and spending — ETH on fees.
| Wallet | Bridges | IMD sent to burn | ETH spent | Last bridge |
|---|
Every IMD transfer into the two BurnExecutors on Ethereum, grouped by where it came from. Moves between the two executors are left out.
Community coins: the LaunchpadHook's burn fee on every community-coin trade, sent in batches. IMD/ETH pool: the CappedBurnHook on the main IMD/ETH Uniswap v4 pool, plus a few other v4 routes. Swarm launches: contracts launched through imd.fun that pass IMD to the executor. Named wallets send IMD by hand.
Community coins (communitycoins.imd.fun) pay a burn fee in IMD on every trade. Swarm launches (imd.fun Launch, Ethereum) are listed when they have burn contracts or have sent IMD to the BurnExecutor. Ordered by IMD sent to burn.
— of — launched tokens with a burn feature have sent IMD to burn so far: — IMD in total.
| # | Token | Type | IMD sent to burn | Trades | Volume ETH | Launched | Address |
|---|
All IMD comes from the 10,000,000 minted once on Base; the Ethereum and Robinhood tokens are backed by IMD locked in the Base bridge contract, so Base's total supply is the whole supply.
Base is split into the Fren Pet token's own burns and the IMD that arrives through the BurnExecutor. Ethereum and Robinhood are small enough to barely show as bars; each bar is labeled.
Burned via burn(): tokens destroyed by the Base token's burn function, measured as 10,000,000 minted minus today's Base supply, split into the Fren Pet token's own burns and the BurnExecutor's. Sent to burn wallets: tokens held by 0x…dEaD, 0x…0000 and 0x…0001, which no one can spend.
| Route | Burned via burn() | Sent to burn wallets | Total burned |
|---|
Circulating IMD on each chain. Base's own totalSupply also counts the IMD locked in the Base bridge contract that backs every bridged token on Ethereum and Robinhood, so Base is shown without it. Added up, the three chains equal Base's total supply and stay below the 10M start.
| Chain | Circulating on chain | totalSupply() | Locked for bridges | Block | Contract |
|---|
All chains: — IMD circulating, against Base's totalSupply of — (— in transit on the bridge).
Ordinary bridging (IMD locked on Base and minted on Ethereum or Robinhood, or burned there and released on Base) is not counted: it moves IMD, it doesn't remove it.
Last refresh — · last request —: — · — Updates run on request, at most once a day.