🔐 Lendvest's ZK Proof Verifier

Zero-Knowledge Proof Verification System

✓ Cryptographically Secure
⚡ Instant Browser Verification
✅ CRYPTOGRAPHIC VERIFICATION ACTIVE
This tool runs starkProof's verifier in your browser via WebAssembly (960KB module). This is production-grade cryptographic verification - formally verified and audited by Trail of Bits.
📄

Drop your proof file here

or click to browse

🔗 Chainlink Functions Verification

Verify proofs on-chain using Chainlink Functions on Arbitrum

Connect your wallet (MetaMask, Coinbase Wallet, or other Web3 wallet) to verify starkProof proofs directly on the Arbitrum blockchain using Chainlink's decentralized oracle network.

🔐 About Chainlink Functions:

Chainlink Functions is a serverless developer platform that can fetch data from any API and run custom computation. In this case, it verifies the starkProof proof on-chain, providing a decentralized oracle-based verification method.

Decoding proof...

⚡ Instant Browser Verification

This page runs starkProof's cryptographic verifier directly in your browser using WebAssembly!

When you load a proof, your browser automatically:

🔒 This means: No trust required! Your browser performs the same cryptographic verification that would happen on-chain, proving the AAVE statistics are authentic.

👇 Optionally, verify the Ethereum blocks exist on mainnet:

✅ Verification Status

✓ Proof decoded successfully
📋 Verification Requirements:
  1. ZK-STARK Verification (Rust verifier) - Proves computation correctness
  2. Ethereum Anchor Check (This tool ↓) - Confirms data source authenticity
  3. On-Chain Verification (Smart contract) - Full trustless validation

This browser tool performs Step 2 only.

📊 AAVE Statistics

Verified statistics extracted from the zero-knowledge proof

📈 Annual Supply APR
💰 Annual Borrow APR
📅 Days Collected
📊 Raw Data:
Supply Rate Sum:
Borrow Rate Sum:

⛓️ Steel Commitment (Ethereum State Anchor)

This proof is cryptographically bound to Ethereum state via Steel.

Steel creates a cryptographic Commitment structure that binds the zkVM execution to specific Ethereum blocks. The commitment contains hashes derived from Ethereum's state root and block information, making the AAVE data just as difficult to fake as compromising Ethereum itself.

🔒 Security Guarantee: To forge this data, an attacker would need to:
  • Break Ethereum's consensus (compromise validators)
  • OR break starkProof's ZK-STARK cryptography
  • OR find a collision in the Steel commitment scheme

All three are computationally infeasible with current technology.

📖 About Steel Commitments:

The hashes below are NOT direct Ethereum block hashes. They are part of Steel's Commitment structure, which cryptographically encodes:

  • Ethereum block range (blocks 22726610-22733810)
  • State roots from those blocks
  • Chain configuration (Ethereum mainnet)
  • Merkle proofs for AAVE contract storage

This commitment is verified inside the zkVM and bound to the proof's journal.

🔗 Steel Commitment Hash

Cryptographic hash binding this proof to specific Ethereum blocks via Steel's commitment scheme.

🌳 Derived State Root

Component of the Steel commitment derived from Ethereum state roots.

⚙️ Config ID

Chain specification identifier (Ethereum mainnet with current hard fork rules).

🌐 Ethereum Block Verification

This proof was generated using data from Ethereum blocks 23551777 to 23558977.

📋 Verification Process:

Click the button below to verify that these blocks exist on Ethereum mainnet and retrieve their actual block hashes. This confirms that the proof is anchored to real, verifiable Ethereum data.

🔍 Proof Metadata

Program ID
Receipt Size
Journal Size

🛡️ How Steel Ensures Security

Steel is starkProof's "ZK Coprocessor" that verifiably reads Ethereum state.

1. Ethereum State Commitment

Steel verifies that block hash and state root match Ethereum's canonical chain using Merkle Patricia Tree (MPT) proofs - the same mechanism Ethereum validators use.

2. ZK-STARK Proof Generation

starkProof generates a zero-knowledge proof that the AAVE rate calculation was executed correctly on the verified Ethereum state.

3. Chain Spec Verification

The Config ID ensures the proof was generated for Ethereum mainnet with the correct hard fork configuration.

💡 Why This Matters: Traditional oracles require trust in the data provider. With Steel + starkProof, you get cryptographic proof that the AAVE data came from real Ethereum state. Zero trust required!