Security and verification
ZK.
Plonky3 STARKs over the KoalaBear field (
2^31 − 2^24 + 1). Poseidon2 + FRI. No trusted setup.- STATUS
- Testnet
- CRATE
- tenzro-zk
- STABILITY
- Stable
- REFERENCE
- Plonky3
01
Why STARKs
Transparent setup (no ceremony), post-quantum-conjectured soundness, ~64–128 KB proofs that verify in ~5–20 ms on commodity hardware.
02
Pinned config
log_blowup 1
num_queries 64
query_pow 16
commit_pow 8
p3 git rev 32079474b1d31d9221656ae774afb322d2597db003
AIRs
Three concrete AIRs: inference, settlement, identity. verify_proof_envelope(&Proof) dispatches by circuit_id.
04
Commitment model
Validators verify Plonky3 proofs off-EVM. They record a 32-byte SHA-256 commitment in the ZkCommitmentRegistry. The EVM ZK_VERIFY precompile is an O(1) HashSet lookup.
Related