Inspect public metadata for the protocol's Groth16 zero-knowledge proofs. The ZK explorer favours selective disclosure and minimal exposure of proof artifacts.
Live application state and user actions are enforced by the Express service and its PostgreSQL database. The Solidity contracts deployed to Sepolia are reference implementations, not the live runtime execution path.
The ZK proof explorer indexes Groth16 proof records generated by the Forge Ecosystem — primarily Proof-of-Space-Time challenge responses, shielded transfer proofs, and ascension burn proofs. For each proof record, the explorer shows: proof type, circuit identifier, block height at generation, timestamp, and verification status (pass/fail). This minimal metadata allows third parties to confirm that a proof was generated and verified without learning anything about the underlying private inputs.
The ZK explorer intentionally omits raw proof artifacts (π_A, π_B, π_C elliptic-curve points), chunk hashes, Merkle paths, and any witness data that could allow a third party to reconstruct or replay a proof. Wallet-linked proof counts and per-wallet proof histories are not exposed in the public explorer view. The design follows the threat model: proof explorers must expose only minimal public metadata and must not reveal artifacts usable for impersonation or re-identification.
Forge Ecosystem proofs use the Poseidon-1 circuit on the BN254 elliptic curve, compiled with snarkjs. The proving key and verification key artifacts are stored server-side and never exposed through the API. A Schnorr–Fiat-Shamir proof system serves as a fallback when the full Groth16 circuit is unavailable. The explorer shows which system generated each proof record, allowing external auditors to identify the provenance of each verification.
Live data snapshot
ZK Proof Statistics