The Natural Order of Kaspa Transactions
Transactions are the heartbeat of any blockchain system, enabling the transfer of digital assets between accounts. While they may seem fleeting to the average user, the information they carry is etched into the blockDAG’s history. Let’s break down the journey of a Kaspa transaction from start to finish.
- A user kicks off a transaction, selecting UTXOs (unspent transaction outputs) to send to the intended recipients.
- The wallet software crafts the transaction and sends it to a connected node. The node adds it to its mempool, shares it with other nodes, and waits for it to be included in a block. If it’s not included within 60 seconds, it’s dropped and must be resubmitted.
- Miners request a block template from the node, which includes transactions from the mempool. They then work to find a special number, called a nonce, that will make the block hash acceptable under the current difficulty level.
- When a miner succeeds in creating a valid block, they submit it to the node for verification.
- The node checks the block’s validity, then broadcasts it across the network. Other nodes validate it too. If an older block is found that should have come before this one and it uses the same UTXOs, the newer transaction is canceled to prevent double spending.
- Network nodes confirm the new block and its transactions, add it to their blockDAG, update the UTXO set, and remove any included transactions from their mempool.
- As more blocks pile on top of a transaction, it becomes harder to alter or reverse. Generally, a transaction is deemed “confirmed” after a certain number of additional blocks (often 10) have been added.
- If a transaction is ever changed due to a blockDAG reorganization, related UTXOs are adjusted or removed as needed. But after 24 hours on Kaspa, transactions are “cemented” and immune to reorganization.
Once a transaction has enough confirmations on the blockDAG, it’s permanently recorded in the public ledger as part of a block, forever part of Kaspa’s history.
Tip: Kaspa currently processes about 200 transactions per second, with a potential increase to 6400 TPS after updates.
For more information on Kaspa, check out these resources:
- KASPA Official Website
- Kaspa on Medium
- Kaspa on Teletype
- Kaspa Discord Channel
- Kaspa Telegram Group
- Kaspa Twitter Page
- Kaspa Reddit Community
- Kaspa on GitHub
- Kaspa Block Explorer
Feel free to comment or ask questions below.
You can also chat with me on the Kaspa Discord — look for Bubblegum Lightning.
This article originally appeared on Kaspa’s official blog.