Trust

Security

The security review, the trusted setup, and the known limits.

Status

SHADOW passed an internal security review before mainnet. It found no way to steal, mint or double spend; the findings it did raise (indexer liveness, a fee bypass, guard bypass, root history) are fixed and covered by tests.

Trusted setup

Groth16 needs a proving key made in a ceremony. Phase 1 is the PSE perpetual powers of tau (80 contributions). Phase 2 has 1 contribution and a random beacon: the hash of the Solana mainnet blockhash of slot 458,966,400, announced publicly before that slot was produced.

• Beacon blockhash: 6TC4GYsCBBeKUDWSsuVAD8srh4fyUS4znqxHcr45Pe5m
• Final proving key SHA-256: 935e1bd76f59a2b5bb9363e67dce829493525e9846d0e9dbc2569702ed9aa85c

An open ceremony with independent contributors will replace this key; existing notes stay valid through it.

In your browser

• Your keys exist only in the page's memory and disappear when you close or reload it.
• The proving files are checked against hashes built into the app before any proof.
• A strict content security policy limits what the page can load and where it can connect.
• Your local activity history is encrypted with a key from your private account.

Known limits

• During the beta the team holds the program's upgrade key. It moves to a multisig before limits are raised.
• If the deposit guard is offline, deposits pause; withdrawals keep working.
• Pausing the pool only stops deposits. Nobody can freeze withdrawals.