UTXO
Pages grouped by this topic tag.
UTXO To Virtual State To IndexerWorking Model BridgesHow spendable state, consensus processing, and observation layers connect without collapsing into one layer.Where Coins Live: UTXOFirst ContactA first-contact explanation of outputs, inputs, outpoints, validation, and spendable state.Transactions, UTXO, Fees, And MempoolTransactionsTurn ownership, UTXOs, transaction format, mass/fees, mempool admission, and accepted evidence into one source-backed learning path.UTXO Model And OwnershipTransactionsKaspa ownership is best taught as spendable outputs rather than account balances.Transaction StructureTransactionsA transaction is a structured object interpreted by validation, hashing, signing, mempool, RPC, wallet, and block-template code.Inputs, Outputs, And OutpointsTransactionsInputs, outputs, and outpoints are the vocabulary of UTXO spending.Transaction ID, Full Hash, Payload Digest, And Rest DigestTransactionsTxid and full transaction hash must be explained separately because they answer different identity and commitment questions.Sighash And Signing CommitmentsTransactionsSighash defines what a signature commits to and is one of the highest-risk wallet/developer surfaces.Mass, Fees, And Storage MassTransactionsMass is resource accounting, not just a fee-size synonym.Transaction Validation LayersTransactionsTransaction validation is layered, and each layer rejects different classes of mistakes.Mempool Policy, Orphans, RBF, And RelayTransactionsMempool admission is local node policy and not final chain acceptance.Block Templates And Transaction SelectionTransactionsBlock templates turn node state and mempool candidates into miner work.Accepted Transaction EvidenceTransactionsAccepted evidence is the boundary between transaction intent and consensus-visible consequence.RPC, UTXO Index, And Explorer BoundariesTransactionsRPC and indexer shapes expose transaction data to tools, but they do not replace consensus source review.Source Path For Transaction ContributorsTransactionsTransaction contributors need a guided source order so a change does not silently break hashing, signing, mempool policy, RPC, or accepted evidence.