[MIDNIGHT VERTICAL]

Security checks for privacy-first Midnight apps.

Privacy tech doesn't mean bug-free. Grid checks the things that make or break a Midnight app: what your contract actually reveals, whether your proof server leaks private data, and how your app code handles secrets.

01Why this matters

Private by default is not safe by default.

Midnight keeps your data private unless you explicitly disclose() it, but the compiler only stops accidentalleaks. It won't catch an access check that anyone can bypass, a secret value that can be guessed, or a proof server quietly pointed at a remote host. Those are the bugs that drain funds and expose users.

02Coverage

What Grid reviews

Smart Contracts

Bugs that let someone bypass your access checks, leak private data, replay a transaction, or get the math wrong. The mistakes that are unique to Compact.

Proof Servers

Your proof server sees users' private data in the clear, so it has to run on their own machine. We flag setups that send it to a remote or shared server.

App & SDK Code

The code around your contract: secret keys ending up in logs, private data sent to the wrong place, and wallet handling that leaks.

03Process

How an audit runs

01

Paste

Drop in your contract, proof-server config, or app code.

02

Analyze

We check for the known Midnight bugs and point you to the exact line.

03

Report

Clear findings, ranked by severity, each with a fix you can act on.

04

Certify

Optionally save a tamper-proof receipt of the audit on-chain.

Audit your Midnight contract now.

Free and instant. It runs in your browser, and nothing is uploaded.