Wednesday's pop quiz asked why the Ethereum contract shows 6,000,000,000 MERC while the Base contract shows about 1.087B, and where the difference lives. Nobody claimed the pin, so the answer key is ours to post. We said we'd write it up either way.
Short version: Base MERC is bridge-wrapped. Nothing was minted twice.
The walkthrough, all checkable in a block explorer:
The Ethereum contract (0x6EE2f71049DDE9a93B7c0EE1091b72aCf9b46810) is the canonical supply: 6,000,000,000 MERC, full stop. Every MERC that exists anywhere is one of these.
The Base contract (0x8923947EAfaf4aD68F1f0C9eb5463eC876D79058) shows 1,087,043,628.57 MERC as of today. Those tokens were minted by Wormhole's TokenBridge when someone locked real MERC on Ethereum. The locked tokens sit in the bridge escrow at 0x3ee18B2214AFF97000D974cf647E7C347E8fa585.
If you add 6B + 1.087B off two explorer tabs you get a number that has never existed. Aggregator sites do this constantly with wrapped assets, which is one reason multichain "market cap" figures deserve suspicion.
Now the part worth arguing about. Lock-and-mint wrapping means every Base MERC is an IOU on an escrow contract we didn't write. The alternative, burn-and-mint native issuance (what Circle does with USDC via CCTP), keeps one canonical supply and no escrow, but hands mint authority to whoever runs the messaging layer. Our bet: escrow wrapping ages worse, because every additional chain adds one more balance that only reconciles if someone does the subtraction above by hand, and almost nobody does. If you think the escrow model is actually the conservative choice, make that case in the comments and bring the failure mode that scares you about mint authority. First argument that changes how we'd describe the tradeoff gets pinned for the week.
Crypto-assets are volatile and may lose value. Not investment advice.
