UTXO Model And Ownership | Kaspa One Stop

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#

Kaspa ownership is best taught as spendable outputs rather than account balances. 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 WIKI-UTXO, RK-TX, RK-UTXO-ENTRY, RK-UTXO-DIFF, RK-RPC-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 UTXO Model And Ownership, the model is built around these anchors: transactions create outputs that may later become UTXOs after accepted-state updates; unspent outputs become spendable UTXOs carrying amount, script public key, DAA score, coinbase flag, and optional covenant ID; later inputs reference previous outputs by transaction outpoint and output index; wallet balances are derived observations from spendable outputs, not account fields; DAG ordering and mempool policy are separate layers. 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. transactions create outputs that may later become UTXOs after accepted-state updates. Virtual state is the bridge from ordered consensus consequences into the state surfaces that tools can inspect. Mempool visibility says a node is considering a transaction; accepted evidence says the transaction was incorporated through consensus processing. UTXO diffs, accepting data, and indexer replay are the review trail for applications that need durable state.

2. unspent outputs become spendable UTXOs carrying amount, script public key, DAA score, coinbase flag, and optional covenant ID. 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. later inputs reference previous outputs by transaction outpoint 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.

4. wallet balances are derived observations from spendable outputs, not account fields. Wallet pages have to keep authority and evidence separate. The wallet controls keys or signing flow, derives addresses, builds transactions, and presents balances from UTXO information. The network decides whether a transaction is accepted. A useful wallet guide checks backup, network selection, node connection, signing, broadcast, decode, and accepted evidence as separate steps.

5. DAG ordering and mempool policy are separate layers. Mempool and relay behavior describe what a node is willing to hold, replace, forward, or package; they are not final acceptance. Block templates are candidate work for miners, and they can change as node state or policy changes. The guide names each stage separately: built, signed, submitted, admitted, relayed, templated, mined, and accepted.

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 transactions create outputs that may later become UTXOs after accepted-state updates.	Use WIKI-UTXO, RK-TX, RK-UTXO-ENTRY; name the stage: built, signed, validated, admitted, templated, mined, or accepted.
2	Check unspent outputs become spendable UTXOs carrying amount, script public key, DAA score, coinbase flag, and optional covenant ID.	Use WIKI-UTXO, RK-TX, RK-UTXO-ENTRY; name the stage: built, signed, validated, admitted, templated, mined, or accepted.
3	Check later inputs reference previous outputs by transaction outpoint and output index.	Use WIKI-UTXO, RK-TX, RK-UTXO-ENTRY; name the stage: built, signed, validated, admitted, templated, mined, or accepted.
4	Check wallet balances are derived observations from spendable outputs, not account fields.	Use WIKI-UTXO, RK-TX, RK-UTXO-ENTRY; name the stage: built, signed, validated, admitted, templated, mined, or accepted.
5	Check DAG ordering and mempool policy are separate layers.	Use WIKI-UTXO, RK-TX, RK-UTXO-ENTRY; 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.