MIXmixer concept
WalletSearch

-Bitcoin started as proof of work: scarce money and ownership that does not depend on who already holds the coins.

-Proof of stake replaced work with capital. That is a different system.

-Kaspa kept Bitcoin’s proof of work and upgraded it: 10 blocks per second on average, now programmable.

mixer concept · Parker inspects. STP doors. PegLab depegs. Live DAG. No price talk.

Four doors · STP

Who is reading.

Four lessons, beginner to expert. Each door keeps the same principles, then shows Parker’s Kaspa models so you can break a rule instead of reading a brochure.

Door 1
BeginnerDigital cash. Proof of work. Parallel blocks stay. Inclusion is not acceptance. Door 2
IntermediateStill PoW. A DAG is not a double-spend pass. Live versus later. Door 3
AdvancedSkip the pitch. Toccata live. Tooling young. A live rule is not an app. Door 4
ExpertPrice is not a protocol. Speed is not a new security story.

I am… each chip opens the matching door.

New to cryptoKnows crypto, not KaspaKnows KaspaKnows crypto and KaspaThinks they know cryptoMoonboy crypto broInstitution (speculative)Tech influencerMoonboy influencerCyberpunkHigh-tech from another chainOther

Parker · learn

Understand what happens to your payment.

Kaspa is a proof-of-work network for sending KAS. Miners can create blocks in parallel. Follow how those blocks become an ordered history, and what makes a payment valid.

Start with the basics Try an interactive model

Explanations you can inspect. Sources you can check.

Parallel blocks, one accepted paymentBlocks B and C both reference A. A later block D references both B and C. The example also shows a payment accepted in the resulting history. Keeping parallel blocks does not make conflicting payments valid.Work can arrive in parallelABCDParallelOne payment accepted
Illustration of parallel blocks and a payment. This is not live network data.
Two miners. One network.
Two miners. Two independent blocks.

Miner 2 found C before hearing about B. Both blocks build on A.

Arrows reference earlier blocks.
A BLOCK earlier TRANSACTIONS Earlier block B BLOCK ref A TRANSACTIONS Miner 1 · 100 ms C BLOCK ref A TRANSACTIONS Miner 2 · 400 ms A BLOCK earlier TRANSACTIONS Earlier block B BLOCK ref A TRANSACTIONS Miner 1100 ms C BLOCK ref A TRANSACTIONS Miner 2400 ms
Inspect the timing
Adjust the delay and inspect a block

An illustrative two-miner model. Discoveries stay fixed at 100 and 400 ms. The same delay applies both ways. Packet positions show elapsed delivery, not physical distance.

Model assumptions and event times

Delivery occurs before discovery at an exact tie. Real mining is random. D is a possible later block, not a timed discovery. This example calculates neither GHOSTDAG nor confirmation confidence.

TimeEvent
0 msBoth miners know A.
100 msMiner 1 finds B, referencing A.
400 msMiner 2 finds C, referencing A.
600 msMiner 2 receives B.
900 msMiner 1 receives C.
Follow the blocks and the information between them

Try a spending rule.

Local illustration · no wallet or network funds

3 coins for one digital tool

Buyer and seller assetsBuyer owns three coins. Seller owns a digital tool.BuyerSeller3 coinsDigital tool0 coins

The buyer has the coins. The seller has the digital tool.

How Kaspa checks this

SilverScript expresses spending conditions. Kaspa nodes check them when an output is spent. In the workshop, Argent coordinates approvals and transaction steps.

The helper must stay within the crop limit and receive at least one resource. Wood is this example’s choice; the condition does not require wood or a particular recipient.

The work task uses a custom verifier: both numbers must be whole numbers from 1 to 15, add to 13 and multiply to 42. This is a specific arithmetic check.

The tool is digital. These rules do not verify delivery of physical goods. The coin illustrations omit fees.

A route through the essentials

Start at the beginning or open the topic you need. Each explanation includes something to inspect or try.

  1. 01Understand the network

    See why blocks can arrive in parallel while a payment can spend an output only once.

    Open explanation
  2. 02Follow a payment

    Trace the payment, change and fee, then inspect what acceptance establishes.

    Open explanation
  3. 03Test a spending rule

    Try a forbidden withdrawal and discover what a signature cannot authorize.

    Open explanation
  4. 04Evaluate the tradeoffs

    Connect speed, mining, validation and application claims to their assumptions.

    Open explanation

Kaspa Graph Inspector

A modest live view of the blockDAG. Open it in its own tab if the frame is quiet.

Open kgi.kaspad.net
If the frame is blank, the inspector blocked embedding. If the picture stops, treat it as paused, not as a failed network. The link still works.

Playground

Bring your tKAS.
See the rules.

Log in with Kasware on Testnet 10, make a local test wallet, or paste a kaspatest: address you already mine to. The models do not spend your coins unless you send.

Open the playground

Sprout Harbor · Testnet-10

Play a small KAS economy.

Build a greenhouse, pay Pip, sell the harvest, deliver the food. Parker’s town, on free test coins. Production and physical delivery are game rules.

Enter the town

Also here