Transaction V1

What this page explains#

Transaction 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. This page sits in Toccata. It gives the topic a plain-language handle first, then shows the working idea, the mechanism, the source trail, and any limits that still matter. This category treats Toccata as a cluster of related changes rather than one feature. Transaction v1, compute budget, script pricing, lanes, sequencing commitments, covenants, and ZK have to be read together when an application depends on them.

The writing follows a simple Kaspa documentation pattern: answer the practical question first, then link outward for details. The closest public sources for this page are DOC-TOCCATA-TX-V1, KIP-0024-PR, RK-TX, RK-TX-SERDE, RK-HASH-TX. Local notes can help choose what to explain, but public-facing references resolve to upstream websites, repositories, papers, release pages, or docs.

How to think about it#

The practical model starts by naming the layer that owns the topic: wallet use, node operation, consensus, transaction validation, Toccata script behavior, tooling, or research. From there, the page shows which public source can support the explanation and where the explanation becomes incomplete.

For Transaction V1, the model is built around these anchors: implemented v1 transaction fields select the transaction rule context under review; KIP-0024-PR design text remains proposed unless merged evidence is attached; subnetwork ID, gas, and payload carry lane/application context in source-backed transaction paths; covenant fields affect outputs and signing context when supported by transaction, RPC, and sighash source paths; txid/full hash/sighash boundaries need separate review; protocol and RPC transaction models preserve checked v1 fields; wallet, SDK, and indexer compatibility remains unknown until exact paths are checked. This model is useful, but it does not encode every constant, branch, error type, or edge case. Those details belong in the source path and the source notes.

How it works#

1. implemented v1 transaction fields select the transaction rule context under review; KIP-0024-PR design text remains proposed unless merged evidence is attached. Toccata pages need to keep the feature cluster separated by evidence type. Release notes and current source can support deployed context; open KIP PRs describe proposal-shaped details; wallet, RPC, SDK, indexer, script, covenant, and ZK behavior each needs its own source path before the guide presents it as current.

2. subnetwork ID, gas, and payload carry lane/application context in source-backed transaction paths. Lanes, subnetwork IDs, gas, and payload fields are application-facing transaction surfaces. The page explains what must survive serialization, signing, wallet handling, RPC submission, indexer decoding, and replay. It also separates reserved or special contexts from ordinary user operations so app designers do not borrow a field without checking its source meaning.

3. covenant fields affect outputs and signing context when supported by transaction, RPC, and sighash source paths. Covenants make Toccata stateful in the UTXO sense: a spend consumes an existing output, script logic inspects the transaction context, and the successor output must carry the allowed next state. The page should keep covenant state, covenant ID, authorization context, indexer head tracking, and negative successor checks separate.

4. txid/full hash/sighash boundaries need separate review. The full transaction hash is a wider commitment surface than the ID used for ordinary references. The page should state which fields are included, which digest path is being discussed, and why tooling that caches only a txid may miss data that matters for v1 payload or rest-digest review.

5. protocol and RPC transaction models preserve checked v1 fields; wallet, SDK, and indexer compatibility remains unknown until exact paths are checked. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.

This mechanism section separates current release/source details from proposal-shaped KIP text. Transaction v1, script pricing, lanes, sequencing commitments, covenants, and ZK are related, but each has its own source boundary.

How to check it#

When using this page for Toccata material, separate deployed release/source details from open KIP or PR-shaped details. Transaction v1, lanes, sequencing commitments, script pricing, covenants, and ZK each need their own source boundary before the page presents them as current behavior.

Related Pages#

• what-toccata-changes
• toccata
• compute-budget-and-script-pricing