The source never leaves you in the clear
One auditor reads it, from a read-only GitHub grant, and nobody else. The seal names a hash of the bytecode, so what is checked is what is sealed.
zkCheck
Prove the code is safe. Show nobody the code.
A zk review on Robinhood Chain: your security checked, your privacy kept. Eight fixed checks proven inside a zkVM, a signed review, an auditor's stake behind it. Nobody sees the source.
Checked by a machine that shows its work
Signed by someone with money behind it.
Connect the repo. Get the zk review. Wear the seal.
Connect GitHub, name the contract
read-only · one repo · one commit
The zk review runs
The repo is compiled and matched to the code on the chain, byte for byte. Then eight checks, fixed and public, run inside a zkVM and come out as a proof. Then a model reads the source and the auditor signs what it says.
Sealed against the hash,
readable by anyone
The code goes in. Only the seal comes out.
This is the zk review. What the chain receives is a hash, a proof and a signature. It never receives the source, and the proof does not contain it either. Anyone can check the proof against the hash, which is why a launchpad, a wallet or a marketplace can show the mark without asking anyone.
The list of checks is short on purpose. A seal is a floor, not a ceiling, and the rules page says what it does not look for.
- Checks
- 8
- Proven
- 8
- Opinions
- 1
SourcezkVMSeal
The eight checks. Fixed, public, and the same for everyone.
- 01No hidden mint
No path creates supply after deployment other than the ones declared in the interface.
- 02No owner drain
No function lets one address move balances that are not its own.
- 03Tax under the cap
If there is a tax, it is fixed or bounded, and the bound is ten percent.
- 04No blacklist
No function can stop a specific address from selling.
- 05No pause on transfer
Transfers cannot be switched off after launch.
- 06Not upgradeable
No proxy, no delegatecall to an address that can change.
- 07Sell path clears
A buy followed by a sell completes, from a fresh address, on a fork.
- 08No self-destruct
Nothing can remove the code once it is sealed.
Privacy, checked inside security.
Every audit so far has asked the same price: publish the code, then we will tell people it is safe. A zk review takes the security check and leaves the privacy where it was. Here is the line, exactly.
STAYS PRIVATE
- The sourceRead by one auditor from a read-only grant. Never stored past the review, never published.
- The repoIts name, its history, its other branches. The seal records a commit hash, not a link.
- YouNo account on this site. The wallet that pays the fee is the only identity, and it can be a fresh one.
BECOMES PUBLIC
- The hashkeccak256 of the runtime bytecode, which anyone can recompute from the chain.
- Eight answersWhich checks passed, with the proof that they ran on that hash.
- The reviewThe auditor's signed text about what the code does. It describes, it does not quote.
- The auditorTheir key and the stake locked behind this seal.
A seal is not a promise. It is a list.
It says these checks ran on this code and passed, and that someone locked money behind saying so. It does not say the code is good, and it cannot see what the checks do not look for. The list is on the rules page, and it will be in the contract.
Read the rulesEvery seal pays a fee in the token. This is where it goes.
- 50%The auditorWhoever ran the press and signed the review. Paid when the seal is written.
- 25%The cover poolHeld with the auditors' stakes. Paid out to holders of a sealed contract that is exploited.
- 15%BuybacksBuys the platform token on the market. What it buys is burned.
- 10%zkCheckWhat the platform earns.
Who you are trusting, and with what.
- Your sourceNobody. It is encrypted in your browser to one auditor's key. The site never sees it and the chain never gets it.
- The checksMathematics. The proof says they ran on your hash and passed. Anyone can verify it, and the registry does before writing a seal.
- The reviewThe auditor, as a signed opinion. It can be wrong. The seal labels it as an opinion, apart from the proof.
- The stakeThe registry. An auditor's tokens are locked behind every seal they sign, and a passed claim takes them.
Launch with the mark, before the reveal.
A Pons launch, a bot, a strategy for sale: get the zk review before anyone sees the code. Connect the repo, name the contract, and the seal follows the bytecode wherever it is deployed.