Midnight · Compact

Built for private contracts.

Beyond generic smart contract issues, the agents look for problems specific to Midnight and Compact. Your code stays private the whole way through.

Midnight-specific checks

What generic audits miss.

The checklist grows with each audit and with community feedback.

  • Accidental disclosure

    Private witness data written to the public ledger, or values that reveal private data indirectly.

  • Linkability

    Patterns that let observers link several transactions to the same user.

  • Maintenance authority

    A single key able to replace circuits and bypass the contract's own access rules.

  • Unstable hashes

    Hash or commitment functions that may change between compiler versions, so a later recomputation no longer matches.

  • Key and role recovery

    Roles that are lost forever if one secret is lost, with no rotation or recovery path.

  • Missing caller checks

    Circuits meant for one role that any user can call.

GitHub integration and code privacy

Read-only. No clone. Nothing kept.

Source code is never published and never stored long term. Access is scoped to the repositories you select, and you can revoke it at any time from GitHub.

How your code is handled

  • GitHub access is read-only, through a GitHub App, scoped to the repositories you select. Revoke it at any time from GitHub.
  • Repositories are never cloned. Files are read directly from GitHub through the API at the audited commit.
  • Uploaded archives are kept only for the duration of the run, then deleted.
  • Contracts are compiled in a temporary, isolated space to produce the hashes. Build files are deleted right after.
  • Code is sent to the AI provider only for analysis, with settings that do not keep data for training where the provider allows it.
  • Source code is never published and never stored long term.

What 00trust keeps

  • Commit hashes and commit lists
  • File names, line numbers and code fingerprints referenced in findings
  • Compiled hashes
  • Audit memory: findings, verdicts, contract map and agents' notes
  • The report

If a previous commit is no longer available on GitHub, for example after a force push, the diff falls back to a full review of the new commit, while open findings are still checked by their fingerprints.

Security of the platform itself

An audit platform is a target.

So the platform follows the same rules it checks for.

  • Audit workers run in isolated containers with no access to other users' data.
  • The project's code is never executed, only compiled and read.
  • Secrets (GitHub keys, AI keys, registry key) are kept in a secret manager.
  • The registry signing key is kept apart from the web servers.
  • Admin actions are logged.
  • 00trust's own contracts and code are reviewed before launch.
Limits

An AI audit reduces risk. It does not remove it.

  1. 01

    An AI audit reduces risk. It does not remove it.

  2. 02

    A report covers one version of the code. Any change in the code or in the deployed verifier keys means the report no longer applies.

  3. 03

    The audit covers the contract code in scope. It does not cover the front end, off-chain services, wallets, keys held by the team or the economics of the project.

  4. 04

    No report guarantees a contract is free of vulnerabilities.

Projects holding large amounts can use 00trust before or alongside a manual audit by a security firm.

00:00

Nothing is taken on faith.

Start an audit1000 ADA · 3 runs