The Problem With Traditional Blockchains
Bitcoin and most other proof-of-work networks are built around a linear chain of blocks. At any given moment, miners all over the world are racing to find the next valid block. When two miners find a block at roughly the same time, the network must choose one and discard the other. The discarded block — called an orphan — represents real computational work that produces no reward and contributes nothing to the chain's security.
This is not a bug; it is a deliberate trade-off. A single, linear chain is simple to reason about and easy to reach consensus on. But it imposes a strict limit on how fast blocks can be produced. Increase the block rate too much and orphan rates skyrocket — blocks are being produced faster than they can propagate across the network, and the chain becomes unstable. Bitcoin's 10-minute block time exists largely for this reason.
The result is a fundamental ceiling on throughput. You can increase block size or decrease block time, but both approaches hit the same wall: the network cannot process blocks faster than it can propagate them globally without compromising the integrity of the chain.
What a BlockDAG Actually Is
Kaspa takes a fundamentally different approach. Instead of discarding blocks that arrive concurrently, it keeps all of them. The data structure is not a chain but a Directed Acyclic Graph — a DAG — where each block can reference multiple parent blocks, and multiple blocks can coexist at the same "height."
This single change in data structure removes the orphan problem entirely. When two miners find blocks simultaneously, both are incorporated into the DAG. Neither is wasted. Both contribute their proof-of-work to the network's cumulative security.
Key insight: in a blockDAG, parallel block production is not a failure condition to be corrected — it is the intended operating mode. The protocol is designed to handle it gracefully at every block rate from 1 BPS to 100 BPS and beyond.
The challenge that remains is consensus: given a DAG where many blocks exist at each "level," how does the network agree on which transactions are valid and in what order? This is the problem that GHOSTDAG solves.
GHOSTDAG: Ordering the DAG
GHOSTDAG stands for Greedy Heaviest-Observed Sub-Tree Directed Acyclic Graph. The name is technical but the core idea is intuitive: the protocol uses the structure of the DAG itself — specifically, which blocks reference which other blocks — to compute a total ordering of all blocks and transactions.
GHOSTDAG identifies a "main chain" (called the selected parent chain) running through the DAG. Blocks that are well-connected to this chain are treated as part of the consensus. Blocks that are poorly connected — which would indicate either slow propagation or attempted attacks — are still included in the DAG but receive lower priority in the ordering.
The result is that the network can maintain consensus over a large set of simultaneously produced blocks, rather than having to serialize all production through a single chain. The consensus is as strong as Bitcoin's at comparable mining power, but it can support far higher block rates without instability.
Why 10 BPS Is Not the Ceiling
Kaspa currently runs at 10 blocks per second on mainnet. This is already faster than nearly any other proof-of-work network in existence. But 10 BPS is not the target — it is the current operating point on a trajectory that the Kaspa research team has mapped out toward 100 BPS and beyond.
The mathematics of GHOSTDAG scale with block rate in a way that linear chains cannot match. As hardware and network infrastructure improve, the protocol can be updated to support higher throughput without changing the fundamental security model. The research papers underpinning Kaspa have demonstrated formal security proofs at arbitrary block rates, not just at today's 10 BPS.
For a wallet built on this network, this trajectory matters. Kaspa Wallet is designed to handle the transaction volume and confirmation patterns of a high-throughput blockDAG — not just today's 10 BPS, but the 100 BPS that is coming.
What This Means for Your Transactions
From a user perspective, the practical impact of the blockDAG architecture is straightforward:
- Transactions submitted to the network appear in a block within seconds, not minutes.
- Confirmation — sufficient to consider a transaction irreversible for most purposes — happens in approximately 10 seconds.
- The network is not congested by competing transactions the way a single-chain network can be. Parallel blocks mean parallel transaction processing.
- Fees remain low because block space is not artificially scarce — there is no need for a bidding war to get into the next block.
Kaspa Wallet connects directly to Kaspa nodes and monitors the DAG in real time. When you send KAS, you see the transaction propagate and confirm without waiting through multiple block confirmations the way Bitcoin users must. The ~10 second confirmation time is not a best-case estimate — it is the consistent, designed behavior of the GHOSTDAG protocol operating at 10 BPS.
Security at High Speed
A common objection to fast block production is the concern that it weakens security. Faster blocks mean less time for each block to accumulate proof-of-work, and less accumulated work per block can mean a network is easier to attack via a 51% double-spend attempt.
GHOSTDAG addresses this directly. Because parallel blocks are incorporated rather than discarded, the total proof-of-work accumulated per unit of time is much higher than a single-chain network with the same hashrate would achieve. An attacker attempting a reorganization must not only outpace the honest chain but also overcome the combined weight of all the parallel blocks being produced honestly. The security argument is formally equivalent to a traditional PoW chain, with the added benefit that none of the honest work is wasted on orphans.
Kaspa's kHeavyHash mining algorithm also contributes to security by keeping the mining hardware landscape diverse. An ASIC-resistant algorithm means the network is not as dependent on a small number of large-scale mining operations as some other PoW chains. Broader participation in mining means a more resilient network.
BlockDAG vs Sharding and Layer 2
Other approaches to blockchain scalability — sharding, rollups, state channels, layer-2 networks — solve the throughput problem by moving transactions off the main chain or splitting the network into parallel partitions. These approaches add complexity: cross-shard communication, trust assumptions about layer-2 operators, and additional failure modes that do not exist on a monolithic chain.
Kaspa's blockDAG scales the base layer directly. There is no second layer required for fast, cheap transactions — the main network handles them. This simplicity has real security implications: there are no bridge contracts to exploit, no sequencer operators to trust, no withdrawal windows to wait through. What you see is what you get: a fast, secure, proof-of-work network operating at the base layer.
Kaspa Wallet is designed to take full advantage of this architecture. If you want to experience blockDAG transactions firsthand, download Kaspa Wallet for free and send your first KAS transaction — it confirms in about 10 seconds.