Start here

Understand Kaspa. From the beginning.

How can we know who paid whom - and make sure nobody changed the payment record - without one bank or company controlling it?

New to crypto? Start with 01 Already know the basics? Jump to 05: Kaspa

Start wherever you need. You do not have to follow the order.

Start from zero

Emma wants to send Liam 30 dollars. How do we remember that it happened, and how do we check that the payment is valid - without one company controlling the payment record?

Bitcoin

Independent computers can check that Emma's payment is valid. But if there is no single manager, how do they decide which payments enter the record - and in what order?

So far we have followed payments. What if we can also define a rule in advance: money sent to a project is released only if a target is reached, otherwise it can be returned - and a transaction triggers that rule so every computer can verify the same result?

When usage grows

More people want to send payments, run rules, and get answers quickly. How can a network handle more activity without making the computers that verify it too difficult to run?

Kaspa

When updates are created quickly, two miners can find new blocks before either one has heard about the other. If both blocks are valid, must the network immediately keep only one - or can both stay connected?

Want to understand one part more deeply?

Choose a topic that interests you. Each explanation starts from the idea itself, so you can enter without reading the whole path first.

How the network works

Blocks

Several payments can be proposed together as one package, along with information that connects it to what was already recorded. That package is called a block. But if a payment appears inside a block, does that mean it has already been accepted?

Proof of Work

Many computers want to propose the next block, but there is no manager deciding whose turn it is. How can they compete in a way where finding a successful result is difficult, but checking it is easy?

Mining

Proof of Work is the competition. Mining is taking part in it: hardware tries again and again to find a result that meets the requirement. What does it take to participate, and what is the difference between mining Solo and joining a Pool?

Nodes

Your wallet or a website says a payment went through. But how can you check it yourself instead of trusting only them? A computer that receives information from the network and checks it against the rules is called a Node.

BlockDAG

If two valid blocks are created before the miners have heard about each other, both can stay connected and a later block can refer to both of them. That is the basic idea of a BlockDAG. But an agreed order is still needed.

GHOSTDAG

A BlockDAG keeps blocks that were created in parallel. But if they contain conflicting transactions, everyone still needs to reach the same order. GHOSTDAG gives Nodes the same rules for ordering that connected history.

BPS

BPS tells us how many blocks are created each second. But that number alone does not tell us how many transactions can be processed - or when a payment is safe enough to rely on.

Decentralization

Even without one company controlling the network, it can still depend on a small number of people or organizations. Decentralization asks how many people can really verify, mine, and participate independently - and what it takes to do that.

DAGKnight

Sometimes information moves through the network quickly and sometimes more slowly. DAGKnight is designed to let transaction confidence respond to those conditions instead of always working from the same timing assumption.