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#
Mass is resource accounting, not just a fee-size synonym. 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-MASS, RK-MEMPOOL-STANDARD, KIP-0009, DOC-TOCCATA-SCRIPT-PRICING, DOC-TOCCATA-TX-V1. 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 Mass, Fees, And Storage Mass, the model is built around these anchors: compute mass, transient mass, storage mass, and normalized mass answer different questions; storage mass needs populated UTXO context; compute budget and script units affect Toccata-era transactions; fee rate relates fee to normalized maximum mass; wallet fee estimation and consensus mass checks answer different questions. 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. compute mass, transient mass, storage mass, and normalized mass answer different questions. Resource accounting needs its own explanation because size, compute, storage, budget, script units, and fee pressure are not the same thing. A transaction may be structurally understandable and still fail admission or validation if the resource rule is violated. The source path for these claims is usually mass, script pricing, validation, and mempool policy together.
2. storage mass needs populated UTXO context. Resource accounting needs its own explanation because size, compute, storage, budget, script units, and fee pressure are not the same thing. A transaction may be structurally understandable and still fail admission or validation if the resource rule is violated. The source path for these claims is usually mass, script pricing, validation, and mempool policy together.
3. compute budget and script units affect Toccata-era transactions. 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. fee rate relates fee to normalized maximum mass. Resource accounting needs its own explanation because size, compute, storage, budget, script units, and fee pressure are not the same thing. A transaction may be structurally understandable and still fail admission or validation if the resource rule is violated. The source path for these claims is usually mass, script pricing, validation, and mempool policy together.
5. wallet fee estimation and consensus mass checks answer different questions. Resource accounting needs its own explanation because size, compute, storage, budget, script units, and fee pressure are not the same thing. A transaction may be structurally understandable and still fail admission or validation if the resource rule is violated. The source path for these claims is usually mass, script pricing, validation, and mempool policy together.
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 compute mass, transient mass, storage mass, and normalized mass answer different questions. | Use RK-MASS, RK-MEMPOOL-STANDARD, KIP-0009; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 2 | Check storage mass needs populated UTXO context. | Use RK-MASS, RK-MEMPOOL-STANDARD, KIP-0009; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 3 | Check compute budget and script units affect Toccata-era transactions. | Use RK-MASS, RK-MEMPOOL-STANDARD, KIP-0009; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 4 | Check fee rate relates fee to normalized maximum mass. | Use RK-MASS, RK-MEMPOOL-STANDARD, KIP-0009; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 5 | Check wallet fee estimation and consensus mass checks answer different questions. | Use RK-MASS, RK-MEMPOOL-STANDARD, KIP-0009; 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#
- 05-sighash-and-signing-commitments
- transactions-utxo-mempool
- 07-transaction-validation