0x34Fd2127F5340640D366778f05696034a18af917
At launch on 3 Sept 2026 the 10% ops allocation was sent to the wrong contract. The runbook step said "treasury"; the address it used was the ETH vault. The vault was built on purpose to hold ETH and nothing else, so the tokens went into a box with no door.
We can't get it back. Nobody can — not the owner, not us, not a vote. It's the same as a burn, except you can see it sitting there. Nobody else's tokens were touched. The ETH pot, the team wallet, every holder and every airdrop are exactly as they were.
One transfer, block 53,476,806, 3 Sept 2026, from the deployer to the vault. 8,880,000 exactly.
The vault's source is verified (exact match, Sourcify, 3 Sept 2026). It has three functions. None of them can call another contract with data, so none of them can move an ERC-20. This is the entire thing that can send anything out:
// ShroomVault.sol — the only function that moves value out function send(address payable to, uint256 amount) external { if (msg.sender != owner) revert NotOwner(); if (to == address(0)) revert ZeroAddress(); uint256 held = address(this).balance; // ETH balance if (amount > held) revert TooMuch(amount, held); (bool ok,) = to.call{value: amount}(""); // empty calldata = ETH only if (!ok) revert SendFailed(); emit Sent(to, amount, address(this).balance); }
transfer on a token?noapprove on a token?noAsk the chain for the vault's $SHROOM balance. Paste this anywhere that can make a web request:
curl -s https://rpc.mainnet.chain.robinhood.com \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x44C9E8257B2bcD5009cE490F3C27A159f637e7F8","data":"0x70a0823100000000000000000000000034Fd2127F5340640D366778f05696034a18af917"},"latest"]}'
You'll get back 0x…75869c3bbbf9a4e000000, which is 8,880,000 × 10¹⁸. Or with Foundry: cast call 0x44C9…e7F8 "balanceOf(address)(uint256)" 0x34Fd…f917 --rpc-url https://rpc.mainnet.chain.robinhood.com