ZK-Rollup Prover

WHAT IT DOES

This tool provides read-only access to zk-rollup prover and verifier data on EVM chains. It allows developers, auditors, and researchers to inspect verifier contract state, proof verification events, batch commitments, state roots, and verification key hashes. Instead of relying on block explorers or third-party dashboards, you connect directly to the blockchain via your wallet's RPC provider and retrieve raw verifier data. You can check if a verification key hash matches expectations, view proof submission events, query batch IDs and state roots, and inspect the overall verifier contract state. The tool is designed for ZK-rollup development, auditing, and research.

HOW TO USE

Connect your wallet using the BGWallet bridge and select your target network. Choose the query type: Verifier contract state, Proof verification events, Batch commitment & state root, or Verification key info. Enter the verifier or batch contract address. For batch queries, optionally enter a batch ID to fetch a specific batch hash and state root. For verification key queries, optionally enter a verification key hash to compare against the contract's stored VK hash. Click "Query prover data" to execute the query. Results appear in the results panel with formatted JSON output.

TECHNICAL MECHANISM

The tool uses ethers.js v5.7.2 to interact with the blockchain via BGWallet's provider. For verifier contract queries, it calls common verifier methods: verificationKeyHash(), proofCount(), and verifyingKey(). For proof events, it uses eth_getLogs with automatic chunking and halving on limit errors, searching for ProofVerified, VerificationSuccess, and ProofSubmitted events. For batch queries, it calls getBatch(), getStateRoot(), totalBatches(), and latestStateRoot() on the contract. For verification key queries, it retrieves the stored VK hash and optionally compares it to a user-provided hash. All BigNumber values are converted to strings for readable output.

WHAT IT CANNOT SEE

This tool cannot generate or verify zk-SNARK/zk-STARK proofs locally. It cannot validate the cryptographic soundness of proofs programmatically — full proof verification requires specialized cryptographic libraries and is computationally intensive. It cannot detect if the prover is malicious or if the proof was generated correctly without full proof verification. It cannot verify off-chain computation or private inputs that are not exposed on-chain. It cannot determine if a verification key is correct or secure without external verification. It cannot detect if the verifier contract itself has been compromised or upgraded to a malicious version. You are responsible for understanding ZK proof systems and verifying trust assumptions.

PLEASE NOTE

EVM chains only. Supports Ethereum, zkSync, Linea, Polygon, and other EVM chains with zk-rollup verifier contracts. Does not support Solana, Tron, Starknet (non-EVM), SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. Requires a wallet connected via BGWallet to provide the RPC provider. The tool is read-only and does not sign any transactions. Always verify contract addresses and proof data independently before relying on the results.