Groth16
Pages grouped by this topic tag.
ZK, Groth16, And RISC Zero SuccinctToccataTeach inline ZK as a covenant-adjacent proof verification path, while separating proof validity from whole state-transition validity.ZK First Contact And VocabularyToccataZK pages begin by defining proof, statement, prover, verifier, public input, witness, circuit, zkVM program, receipt, journal, tag, and precompile.Inline ZK Covenant ModelToccataInline ZK is best taught inside the covenant loop: current UTXO, proof, script verification, successor output.OpZkPrecompile Tags And CostsToccataTags and costs are high-risk source claims because they decide which verifier runs and whether the transaction has enough budget.Groth16 OverviewToccataGroth16 background explains circuits, witnesses, proving keys, verifying keys, proof bytes, public inputs, and trusted setup context.Groth16 Kaspa Verifier Source PathToccataThe Kaspa Groth16 source path explains verifying key/proof data, public input arity, metering, parsing, and verification failure cases.RISC Zero Succinct OverviewToccataRISC Zero Succinct pages explain zkVM receipts, image IDs, journal commitments, seals, and the difference between upstream concepts and Kaspa stack expectations.RISC Zero Succinct Kaspa Verifier Source PathToccataThe RISC Zero Succinct source path is a verifier-specific review of image IDs, journal digest, seal, control proof, claim, and supported hash assumptions.Proof Binding To Covenant StateToccataProof binding connects verifier success to the covenant state transition the app actually cares about.Negative Cases And Failure MatrixToccataA failure matrix makes ZK safer by naming what must fail.Groth16 Transition StarterToccataThe Groth16 starter is a draft implementation checklist for binding proof output to a covenant transition without citing local lab files as authority.RISC Zero Succinct Transition StarterToccataThe RISC Zero starter is a conceptual checklist until a concrete public upstream recipe is verified, and it makes image ID, journal digest, receipt/seal, and verifier boundaries explicit.Testing Evidence And ReadinessToccataReadiness labels prevent local proof output from being mistaken for production evidence.ZK Source Path And Review PlaybookToccataThe ZK review playbook turns a claim into source work: docs, KIP, tags, costs, verifier source, tests, releases, and claim labels.ZK FAQ And MisreadingsToccataThe ZK FAQ answers the mistakes that cause unsafe designs: valid proof is not whole transition validity, local proof output is not network readiness, and zkVM verification is not on-chain program execution.