In brief
Transaction evidence moves through layers: wallet intent, node or mempool response, block inclusion, virtual processing, and accepted UTXO effects.
What this page explains#
Inputs, outputs, and outpoints are the vocabulary of UTXO spending. This page sits in Transactions, UTXO, Fees, And Mempool. 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 follows a transaction from ownership model to structure, signing, validation, mempool admission, template selection, and accepted-state evidence. The main danger it prevents is collapsing all transaction states into one word.
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 RK-TX, RK-UTXO-ENTRY, RK-RPC-TX, RK-TX-VALIDATION. 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 Inputs, Outputs, And Outpoints, the model is built around these anchors: outpoints identify previous outputs by transaction ID and output index; inputs carry previous outpoint, signature script, sequence, and versioned compute context; outputs carry value, script public key, and optional covenant binding; UTXO entries add amount, script, DAA score, coinbase flag, and optional covenant ID context; covenant IDs add Toccata-era state lineage context. 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. outpoints identify previous outputs by transaction ID and output index. A UTXO explanation begins with outputs that can later be spent. Inputs do not draw from an account balance; they reference earlier outputs by outpoint and provide the data needed to authorize the spend. This is why wallet balance, transaction construction, validation, and covenant state all need the same ownership vocabulary.
2. inputs carry previous outpoint, signature script, sequence, and versioned compute context. Transaction pages mention covenants only as fields, scripts, signing commitments, or validation context. The transaction layer must preserve or check the relevant data, then route state-machine design to the covenant section and proof binding to the ZK section.
3. outputs carry value, script public key, and optional covenant binding. Transaction pages mention covenants only as fields, scripts, signing commitments, or validation context. The transaction layer must preserve or check the relevant data, then route state-machine design to the covenant section and proof binding to the ZK section.
4. UTXO entries add amount, script, DAA score, coinbase flag, and optional covenant ID context. Transaction pages mention covenants only as fields, scripts, signing commitments, or validation context. The transaction layer must preserve or check the relevant data, then route state-machine design to the covenant section and proof binding to the ZK section.
5. covenant IDs add Toccata-era state lineage context. Transaction pages mention covenants only as fields, scripts, signing commitments, or validation context. The transaction layer must preserve or check the relevant data, then route state-machine design to the covenant section and proof binding to the ZK section.
This mechanism section follows a transaction through construction, identity, signing, validation, mempool policy, block templates, and accepted evidence. The stage must be named before the claim is reused.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check outpoints identify previous outputs by transaction ID and output index. | Use RK-TX, RK-UTXO-ENTRY, RK-RPC-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 2 | Check inputs carry previous outpoint, signature script, sequence, and versioned compute context. | Use RK-TX, RK-UTXO-ENTRY, RK-RPC-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 3 | Check outputs carry value, script public key, and optional covenant binding. | Use RK-TX, RK-UTXO-ENTRY, RK-RPC-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 4 | Check UTXO entries add amount, script, DAA score, coinbase flag, and optional covenant ID context. | Use RK-TX, RK-UTXO-ENTRY, RK-RPC-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 5 | Check covenant IDs add Toccata-era state lineage context. | Use RK-TX, RK-UTXO-ENTRY, RK-RPC-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
When using this page for a transaction claim, name the stage precisely: built, signed, validated, admitted to a mempool, included in a template, mined, accepted, or reflected in a UTXO change. Each stage has a different evidence surface and should not be collapsed into a single success word.
Related Pages#
- 02-transaction-structure
- transactions-utxo-mempool
- 04-transaction-id-and-hash-contexts