What zkCheck is
A seal on a contract's bytecode that says a fixed list of checks passed, with a proof, a signed review, and money behind it. The source is never published.
zkCheck answers one question for people who hold or are about to buy a token on Robinhood Chain: has this code been checked, by whom, and what did they put behind it? It answers without asking the developer to publish the source.
The bargain it refuses
Every audit until now asked the same price. To be trusted, publish the code. Then someone reads it, writes a report, and the report says what it says. The source is public for the rest of the token's life, and so is every strategy, every trick and every unfinished idea it contained.
That price is fine for a protocol that wants to be forked. It is not fine for a trading bot, a strategy someone is selling, a launch that wants no front-runners before the reveal, or simply a builder who does not want to hand out their work.
zkCheck takes the security check and leaves the privacy where it was.
What a seal is
A seal is a record written against the hash of a contract's runtime bytecode. It carries three things.
- Eight answers. A fixed list of checks ran on that bytecode and each one passed or failed. The list is public and the same for everyone. Each answer comes with a sentence of evidence.
- A review. An auditor read the source and signed a description of what the code does, who holds which powers and what looks off. It is an opinion, labelled as one, and it never quotes the code.
- A stake. The auditor locked tokens behind the seal. If a sealed contract is exploited through something the checks should have caught, a claim can take that stake.
Everything a wallet, a launchpad or a holder needs is in the seal. Nothing they do not need leaves the auditor.
The word "zk"
The checks are meant to run inside a zkVM, a machine that executes ordinary code and produces a small proof that it ran and produced that output. The proof commits to the bytecode hash and the rule set, so anyone can verify that the checks really ran on this exact code, without seeing the code and without trusting who ran them.
Status. Today the checks run on the auditor's machine and the answers are signed by the auditor's key. The zkVM path is the next step, and every seal carries a field that says which of the two produced it. The two are never confused, on the site or in the record.
What it is not
A seal is a floor, not a ceiling. It says these eight questions had the answer "no". It does not say the code is good, and it cannot see what the checks do not look for: liquidity, who holds the supply, the deployer's intentions, or the constructor arguments of one deployment. What a seal cannot see is its own page, because it matters as much as the rest.