Seal your code

01

The repository

Checking GitHub…

02

The contract

The seal is written against the hash of runtime bytecode. Give the deployed address, or the bytecode if it is not deployed yet. The hash is computed in this tab.

03

The press

The worker compiles the repository at that commit, matches the result to the bytecode byte for byte, runs the eight checks, writes the review, signs the seal. A few minutes. The source is deleted when it is done.

Free while the registry is not deployed. The fee in the platform token comes with it.

What the zk review does

  1. 01
    Reads the repository at one commit

    Downloaded as a tree, never cloned with history, with your grant, for exactly this. The seal records the commit hash and not the repository.

  2. 02
    Compiles it and matches the chain

    Foundry builds it. The runtime is compared to the code on the chain byte for byte, metadata and immutables set aside. No match, no seal.

  3. 03
    Runs the eight checks

    On the compiled contract: supply, balances, tax, blacklist, pause, upgradeability, a transfer in and out on a fork, self-destruct. Each answer comes with a sentence of evidence.

  4. 04
    Writes and signs the review

    A model reads the source and describes what it does without quoting it. The auditor signs hash, answers and review together. Then the source is deleted.

The eight checks. No hidden mint · No owner drain · Tax under the cap · No blacklist · No pause on transfer · Not upgradeable · Sell path clears · No self-destruct.

Checks are signed by the auditor for now. When they run inside a zkVM the seal says so, and the two are never confused.