Addresses
Every address on the site with a link: what it is, who created it, and what you are exposed to by trusting it.
Every address the site reads, in one place, with what it is, who put it on the chain, and what you are exposed to by trusting it. Addresses on the front page are rendered from the script's own constants rather than typed into the markup, so what the page shows cannot drift from what it queries. This page is markdown, so it is the one place where an address is typed by hand; treat the front page and the explorer as the authorities and this list as the explanation.
Everything links to Blockscout, which is reading the same chain your wallet is on.
Not deployed yet
Four addresses are load-bearing for the protocol and none of them exists. The token has not launched, so the distributor cannot be deployed against it, so there is no reserve wallet and no router path. The site shows TBA for all four, the docs footer says published at launch, and none of this documentation will print an address before there is one to print.
| What it will be | Created by | What trusting it costs you |
|---|---|---|
$MEVHOOD token | the PONS launchpad, from a creation transaction anyone can read | the supply, the decimals and the fee routing are the launchpad's, not ours. The threshold of 100,000 only means something against whatever supply this ends up having |
MevhoodDistributor | deployed by us, once, with deploy.mjs | this is the contract that holds claimable ETH. No proxy, no upgrade, no pause. Its full source is in the repository and it should be verified on the explorer before anyone claims against it |
| Reserve wallet | an EOA whose key is the operator's | it is the wallet whose growth defines income, it signs every openEpoch, and it is a plain externally owned account holding funds. See what one key can do |
| Router for the burn | whoever runs the DEX $MEVHOOD graduates onto | it only gets configured after graduation, and until then the burn is skipped on purpose |
The bot
| Address | What it is | Created by | What trusting it costs you |
|---|---|---|---|
0xdc4327aa83100a744a01d888c670a3b3919441a6 | the bot's operator EOA. Every outgoing transaction calls the executor with method id 0x3997deb9 | a person | nothing on the site depends on it beyond being able to say where the executor's traffic comes from. It does not hold your money and is not the reserve |
0xC828E5038D09865872FC99Fe76aE499F60C4Ae9B | the executor. Holds the inventory, does the trading, and is the address the bot panel and the ticker touches read | 0x42d8471C…d7947 | its source is not verified on the explorer. You can read every transfer in and out of it and nothing else. The site's claim is about the transfers, not about the bytecode |
If the executor's address were wrong, the bot panel would be describing somebody else's activity. That exact mistake was made once, with 0x8f10b468b06c6fd214b65f87778827f7d113f996, a shared network factory contract that spent about forty minutes on the production page mislabelled as the bot before it was pulled. The story is on the bot page and it is the reason this page exists in the shape it does.
Fixed addresses and third-party infrastructure
| Address | What it is | Created by | What trusting it costs you |
|---|---|---|---|
0x000000000000000000000000000000000000dEaD | the burn sink. The router delivers bought tokens straight here | nobody; it is a conventional unspendable address | tokens sent here are unrecoverable, which is the whole point. Burned supply is counted from Transfer logs into it, independently of anything we emit |
0xcA11bde05977b3631167028862bE2a173976CA11 | Multicall3, at its canonical address on every chain that has it | the Multicall3 deployers, long before this chain existed | it batches balanceOf reads during the snapshot. A wrong answer here would corrupt a share table, which is why the operator cross-checks the replayed balances against totalSupply() and refuses to publish when they disagree |
0xfB5b5778d45AE47F15323fb59B666c655174A79C | HOOD, Ondo's token of Robinhood Markets stock. $MEVHOOD is paired against it | Ondo | it is the quote side of the pair and nothing else. It carries no Chainlink feed on this chain, so it never appears on the premium board |
0xecA312775BDfEd66f1225263c6992B87D0Ce314E | the HOODon/USDG pool, linked out to Dexscreener | whoever created the pool | a pool quote is what the last trade paid. It is not a price anything could be exited at, and the site labels every pool-priced figure as an estimate |
The seven tokens the bot trades
USDG, WETH, PONS, CASHCAT, BOING, LAMBO and PEPONS, with their addresses and decimals, are in the table on the bot page. Trusting them costs what trusting any third-party ERC-20 costs: the balances the site reads are whatever those contracts report, and USDG reports 6 decimals rather than 18, which a careless formatter gets wrong by twelve orders of magnitude.
The 35 stock feeds and their tokens
Each ticker on the premium board carries a Chainlink feed address and a token address, both generated into the page's constants rather than typed, and every row links out to the pool it was priced against. They are listed on the board itself rather than duplicated here, because 70 addresses in a documentation table is a place for a typo to hide. What trusting them costs is covered in feeds and tokens are somebody else's work.
The endpoints, which are not addresses but are trust
| Endpoint | What it serves | Known limits |
|---|---|---|
rpc.mainnet.chain.robinhood.com | everything: balances, logs, eth_call, the claim transaction | intermittently answers with a duplicated Access-Control-Allow-Origin: *,* header, which browsers reject. A failed fetch is retried; a JSON-RPC error is not |
rpc.ordofi.network | fallback only, and not full redundancy | measured 2026-09-10: keeps balances, the board and the countdown alive, but cannot serve the log-heavy loaders. 36,000 blocks across seven tokens returns -32005 after 25 to 50 seconds; smaller windows fail at random rather than by size |
api.dexscreener.com | pool prices, liquidity and 24-hour volume | an indexer, not the chain. Its liquidity figures inherit whatever it got wrong, which is why the board breaks pool ties by volume |
A claim transaction is signed by your wallet and sent through whichever endpoint your wallet uses, not through the site's. The page's RPC choice affects what it can show you; it does not affect where your transaction goes.
How to check this page against reality
The observer links directly to the executor used for its balance and transfer queries. Cross-check that full address with the explorer. Token, vault and distributor addresses have not been configured; this documentation must be updated and checked against deployment records before claims launch.