NullarkPool, keeps private note material out of public channels, and later exits to a public recipient with a proof-checked withdrawal.
Start with boundaries
See the current public status, contract addresses, and non-approval boundaries.
Review the privacy model
Understand where direct on-chain linkage is reduced and which caveats still matter.
Verify artifacts
Check the pool, verifiers, public input order, trusted setup record, and prover artifact hashes.
Review relayer visibility
Understand relayer metadata, public exits, and request rejection boundaries.
Nullark boundaries
Nullark uses fixed-denomination notes and proof-checked withdrawals on MegaETH. Plaintext note material is not posted as public chain data, and withdrawals prove authorization against accepted pool state before exiting to a public recipient. Nullark does not hide deposits, withdrawals, recipients, fixed amounts, timing, commitments, nullifiers, encrypted-note events, submitter paths, RPC metadata, frontend metadata, relayer metadata, or later wallet behavior.Current public source of truth
public-artifacts/current.json is the machine-readable runtime record. The human-readable pages repeat contract addresses for review, but the JSON artifact remains the canonical value source.