Seal a token that is already live
The code is deployed, holders exist, and you want the badge. Ten minutes if the repository matches.
1. Find the deployment commit
The bytecode on the chain was compiled from a specific commit with specific settings. Find it: the tag you deployed from, the broadcast/ folder Foundry wrote, your deployment notes. If you have verified the contract on Blockscout, the metadata there tells you the compiler version and settings.
2. Check the match locally
Before submitting, confirm your repository at that commit reproduces the chain:
git checkout <commit>
forge build
cast code <address> --rpc-url https://rpc.mainnet.chain.robinhood.com | head -c 80
jq -r .deployedBytecode.object out/Token.sol/Token.json | head -c 80
The first eighty characters should be identical (the tail differs by metadata, which is expected). If they are not, Why bytecode does not match.
3. Submit
/seal: connect GitHub, install the app on the repository, choose it and paste the commit hash as the ref. Deployed on Robinhood Chain, paste the address, Compute the hash to see what will be sealed. Name it. Send.
4. Read the answers
The worker runs all eight, including the fork simulation, since the token has holders. Read every fail and its evidence. The evidence names the function and the path. Three outcomes:
- 8 of 8. The seal is posted on X. Put the link everywhere.
- A fail you can fix. Fix, redeploy, and you have a new token with a new hash; the old one keeps its old seal. Whether to migrate holders is your call. Many projects instead keep the 7 of 8 and the evidence public: honest is a good look.
- A fail you disagree with. The checks are deterministic and documented. Read the check's page under Concepts. If the check is wrong about your code in a way the page does not cover, open an issue with the evidence sentence; a fix to the check is a new rule set version, and every seal records its version.
5. Tell holders what the seal means
Link the seal, not a screenshot. The page has the eight answers with evidence, the review, the commit, the auditor and the signature, and it says signed until the checks are proven. A holder who reads the limits page and then the seal knows exactly what they know.