Toccata
Pages grouped by this topic tag.
Toccata Application LifecycleWorking Model BridgesA status-safe bridge from transaction v1 through covenant state, inline ZK, and based-app observation.Toccata Internals Function WalkthroughContributionToccata internals require cross-module review because transaction v1 touches identity, signing, resource accounting, scripts, covenants, and ZK.CovenantsToccataExplain covenant state, lineage, introspection, covenant IDs, and output constraints with clear implementation and proposal boundaries.Auth Groups Vs Covenant GroupsToccataAuth groups and covenant groups answer different questions and must not be collapsed.Counter Covenant StarterToccataA counter covenant starter is a teaching pattern to verify, not an upstream-endorsed production recipe. It introduces successor checks, negative tests, and state encoding while keeping every concrete rule source-gated.Covenant Design PatternsToccataDesign patterns help readers recognize covenant shapes before building them.Covenant Head Indexer StarterToccataA covenant app needs a reliable way to find the current head after accepted activity and restart.Covenant IDs And LineageToccataCovenant ID is lineage evidence, not the whole app rule.Covenants And StateToccataA covenant is taught as a script-controlled UTXO that validates a spend and the next output, not as account storage mutated in place.Dice RollRegistry Case StudyToccataThe local dice/RollRegistry experience can teach reusable checks, but it is labeled local experience and cited only through public mechanisms.Introspection Opcodes And Script ContextToccataIntrospection lets script logic inspect transaction context, but every inspected field needs a source-backed meaning.Successor Output ValidationToccataSuccessor validation is the covenant safety center: the script must check what the next output is allowed to be.Vault Covenant StarterToccataA vault starter is design-question guidance until a concrete upstream vault implementation, wallet flow, and accepted-evidence path are verified.SilverScript, vProgs, And Based AppsToccataExplain authoring, compiler/lowering, based app architecture, vProgs runtime layers, settlement, indexers, and readiness caveats.Based AppsToccataBased apps use L1 ordering evidence with off-chain execution and settlement, not generic smart-contract calls.Based Lane StarterToccataA based lane starter walks from lane design to ordering observation and settlement evidence.Declarations And Covenant MacrosToccataDeclaration macros are teaching aids for common covenant patterns, but their output must still be reviewed against state rules.Minimal dApp TemplatesToccataTemplate pages organize counter, vault, ZK transition, based lane, and dice-style lessons into source-labeled starters.Settlement And Indexer ResponsibilityToccataSettlement pages answer who reconstructs activity, who proves it, who submits it, and who tracks state after restart.SilverScript AuthoringToccataSilverScript authoring is a convenience layer for writing covenant scripts, not a replacement for protocol review.SilverScript Compiler And LoweringToccataCompiler and lowering pages explain how higher-level declarations become scripts and what still needs manual review.Tooling Readiness And Production CaveatsToccataTooling readiness pages keep moving APIs, pre-check tools, wallet support, and mainnet safety gates visible.User Ops, Payloads, And LanesToccataUser operation pages teach payload encoding, gas, lane namespace, and ordering evidence.vProgs ArchitectureToccatavProgs is treated as evolving reference/runtime work that needs tooling-readiness labels.vProgs ZK PipelineToccataThe vProgs ZK pipeline connects transaction processing, batch aggregation, proof generation, journal/state transition, and settlement as tooling or architecture material, not as base-protocol authority.ToccataToccataExplain Toccata as a sourced upgrade and application surface without blending docs, releases, implementation, proposals, and local experiments.Activation, Releases, And ParametersToccataActivation pages teach how to verify Toccata status without blending mainnet, testnet, and history.Compute Budget And Script PricingToccataCompute budget and script pricing are described through docs, KIP-0025-PR proposal text, and source paths; this page should not treat proposal-only material as final deployed behavior.Sequencing CommitmentsToccataSequencing commitments describe how based-app activity can be committed and proven across lane partitions.Subnets, User Lanes, And GasToccataLanes and subnetwork fields should be taught as application ordering and payload surfaces with source-backed boundaries.Toccata Decision ReferenceToccataThe decision guide asks for the smallest model that carries the invariant: ordinary transaction, covenant, ZK covenant, based app, or vProgs-style execution.Toccata FAQ And Failure ModesToccataThis question-led page corrects common Toccata misreadings before they become unsafe app designs.Toccata Source WalkthroughToccataA Toccata source walk ties transaction fields, hashing, sighash, mass, subnets, seqcommit, txscript, opcodes, and ZK precompiles into one review path.Transaction V1ToccataTransaction v1 is the field-level foundation for Toccata-era application behavior, but implemented source fields and KIP-0024-PR proposal text must be read as separate claim classes.What Toccata ChangesToccataToccata is an application surface made of several connected protocol and tooling changes, not one isolated feature.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.