# Proofs and the verifier Every batch your zone settles to the host chain carries a zero-knowledge proof that the batch is honest: balances add up, nothing was minted without a backing deposit, no withdrawal exceeded its account. You cannot forge it, and you do not have to reveal anything to produce it. That is the whole trick: provable honesty without disclosure.  The proving core is a single pure function, a state transition function written in `no_std` Rust, so the exact same code runs unchanged inside a zkVM, inside a TEE, or in the node itself. That portability is what makes the verifier proof-agnostic: the on-chain verifier sits behind a minimal `IVerifier` interface and does not care how the proof was produced. V1 settles with real SP1 zero-knowledge proofs. The verifier is live on-chain from day one, not a placeholder, so the one-to-one backing is cryptographically enforced now. Because the design is proof-agnostic, a different backend can be swapped in later without touching the portal or the state transition function. :::tip This is what lets you answer a regulator or an auditor with math. You can demonstrate that every unit inside your zone is backed by a locked canonical asset, without exposing a single customer's balance or history. :::