Live Proof Readout

This page exists for one reason: get you to zkde.fi/test with enough context to understand what you're looking at.

Every verifiable claim in these docs — proof lanes, verifier contracts, settlement paths — is cross-testable at that endpoint. It's not a marketing page. It's a backend showcase that exercises the proof pipeline and reports pass/fail for each claim.

What you'll see

The test endpoint at zkde.fi/test runs through the full proof stack and reports results. Here's what it covers:

ModelBridge dual-lane proving

The money shot. EZKL model inference → Groth16 proof → Garaga verification on Starknet. Both ModelBridge (standard) and ModelBridgeHeavy (complex outputs) lanes. Plus the STARK integrity lane via Stone, the Noir HONK bridge, and Native KZG strict mode. All five verifier lanes, exercised and reported.

AI advisory flow

zkML risk scoring and anomaly detection in action. The 13-circuit screening bundle runs against test inputs. Pool safety analysis generates proof receipts. Agent skills get registered and tracked.

Privacy and settlement

Full privacy pool operations — commitment generation, Merkle withdrawal proofs, nullifier verification. The three privacy tiers (strict, standard, express) get exercised. Madara L3 fact registration runs end to end.

On-chain contract state

Live reads from deployed verifier contracts. Receipt registry lookups. Reputation tier checks. FICO-pack proof status. These aren't mock responses — they're actual contract calls.

Transaction evidence

Real verified transactions on Starknet Sepolia. Click through to Voyager and inspect the proof data yourself.

What was proven	Lane	Tx
Standard model bridge proof	groth16_garaga	0x2c8ea...679b
Heavy model bridge proof	groth16_garaga	0x49226...b59c
STARK reputation proof	stark_integrity	0x7249f...739d
Noir HONK bridge proof	noir_honk	0x55f1d...3475
Native KZG strict proof	native_kzg	0x5c9e2...5f42

Core contracts

Contract	Network	Address
ModelBridge Verifier	Starknet Sepolia	0x037c4...626f
ZkmlVerifier	Starknet Sepolia	0x068ab...8923
GaragaVerifier (BN254)	Starknet Sepolia	0x06d0c...6d37
Halo2Verifier (EZKL KZG)	Ethereum Sepolia	0xF7b55...2Ab9
ObsqraFactRegistry	Starknet Sepolia	0x02009...faa3

Reading the report

Each entry in the report has four parts:

1. Claim name — what's being tested ("ModelBridge dual-lane proof with on-chain verification")
2. Status — PASS or FAIL, with timing
3. Evidence — tx hashes, contract addresses, API response snippets, proof artifacts
4. Network — which chain the verification ran on

A fully passing report means everything worked at run time. It's not a promise that every product route is uniformly wired — it's strong evidence that the underlying proof infrastructure is operational.

Programmatic access

The same data is available as JSON:

curl https://zkde.fi/test?format=json | jq '.results[] | {claim: .name, status: .status}'

Or run the showcase script locally:

python3 scripts/hackathon_backend_showcase.py \
  --base-url http://127.0.0.1:8003 \
  --emit-report --emit-report-force --judge-mode

This generates artifacts/hackathon_showcase/latest.html and latest.json.

---

Go look at it. Then come back and read Proof Pipeline if you want to understand the machinery.