Don't trust us. Read the chain.

1. A tier comes from one public call

Your tier is your $MASKHOOD balance at the moment an agent thinks, nothing else. Runs are counted per UTC day. The app makes this call:

// Robinhood Chain (4663), any public RPC
eth_call({ to: <$MASKHOOD contract>, data: balanceOf(<address>) }, "latest")

1. On the Verify pageOpen Verify, paste any address. It shows the call, the block it was read at, the balance and the tier.
2. By handOpen the $MASKHOOD contract on Blockscout (address from the home page), go to Read contract, call balanceOf with the address. Compare with the tiers below.

2. The buyback and burn

Creator fees from Pons go to a public treasury wallet. It buys $MASKHOOD and sends it to the burn address, which has no known key. Three things to check:

1. The treasury receives feesOpen the treasury wallet on Blockscout and look at its incoming transfers from Pons.
2. It buys $MASKHOODIn the same wallet, Token transfers shows $MASKHOOD coming in from swaps.
3. It burns what it boughtEach purchase is followed by a $MASKHOOD transfer to the burn address. The burn address's balance only grows.

3. A mask trade leaves your main address out

1. Open the mask on BlockscoutIn the app, every mask and every transaction has an explorer link.
2. Open the swapThe from address is the mask. Your main wallet is not in the transaction or in its token transfers.
3. Check the fundingLook at how the mask got its first ETH. If it came straight from your main wallet, the two are linked, which is exactly what the app's privacy check warns about.

4. A bridge into a mask

On Robinhood Chain, the incoming transfer goes from the bridge to the mask. On the source chain (Ethereum, Base or Arbitrum) the transaction shows the address you sent from, and LI.FI's explorer connects the two sides. That is honest: a bridge keeps your main address out of the Robinhood Chain transfer; it does not erase the link.

5. An agent stayed inside its budget

1. The planBefore you approve, the app shows the plan the AI returned and each hard rule it passed: allowed token, per-order cap, budget and expiry.
2. The signerThe trade is sent from the agent's own mask. Open it on Blockscout: it can only spend what that mask holds.
3. The totalAdd up the agent mask's outgoing swaps. They can never exceed what it was funded with.

6. Keys stay in your tab

Open your browser's developer tools on the app, Network tab, and use it: the signature and mask keys are never in any request. What does leave the tab: chain calls through the relay, swap quotes, agent mandates for planning, and the signed transactions themselves, which are public anyway.