Skip to content
KAS/USDMARKET CAPHASHRATEBLOCK RATE10 /secBLOCK TIME100 msBLOCK REWARDCIRCULATINGMEMPOOLCONSENSUSGHOSTDAGNODEPREMINENONESUPPLY CAP28.70 B KAS
KAS/USDMARKET CAPHASHRATEBLOCK RATE10 /secBLOCK TIME100 msBLOCK REWARDCIRCULATINGMEMPOOLCONSENSUSGHOSTDAGNODEPREMINENONESUPPLY CAP28.70 B KAS
KASPA UNIVERSITYVERIFY · DO NOT TRUST
Seal of the campus
KASPA UNIVERSITY
OPEN ENROLMENT · NO TUITION · NO SIGN-UP · NO PRICE PREDICTIONS
The rule
Verify. Do not trust.

Every number on this page is either live and labelled, or modelled and labelled. None of them are illustrative.

Kaspa University · open enrolment

Kaspa
University

Nine short courses across four departments: what this network is, what it is honestly good for, how to hold it without losing it, and which projects are worth your attention. No tuition, no sign-up, no price predictions, and no number on this page that is not either live and labelled or modelled and labelled.

At a glance
Courses9
Reading time~87 min total
PrerequisitesNone
TuitionFree · always
Teaching material · live from mainnet
api.kaspa.org · refreshed every 20s
Price
Live market price. This page never predicts one.
Network hashrate
The work defending every confirmation you rely on.
Block reward
KAS
Steps down by 2^(-1/12) every Kaspa month.
Supply cap
28.7BKAS
Fixed at 28,704,035,605. No premine, ever.
The syllabus

Four departments, nine courses, one rule

§ 00 — what you are signing up for

The rule is that a claim and its evidence travel together. Where something is verifiable, this page says how to verify it. Where something is modelled, it says so. Where something has not shipped, it gets no date. Read in order or jump to what you came for.

DEPT 01

Protocol

Consensus, emission, upgrades

Everything the network guarantees on its own, with no third party involved.

DEPT 02

Custody

Keys, backups, threat models

The only department where a mistake is permanent and nobody can reverse it for you.

DEPT 03

Ecosystem

L2s, tooling, data, tokens

Young, moving fast, and the part of the stack most likely to change after you read this.

DEPT 04

Critical reading

Claims, sources, comparisons

How to check a statement about Kaspa — including the statements on this page.

KAS 101 · Protocol

What Kaspa
actually is

§ 01 — foundation, 12 min

Kaspa is a proof-of-work ledger that does not throw work away. That single design decision is what lets it run at ten blocks per second while keeping the security model people trust Bitcoin for, and everything else on this page follows from it.

The lecture in one paragraph

In a single-chain protocol, two miners who find a block at the same moment produce a conflict, and the protocol resolves it by discarding one. That is an orphan. It is tolerable at ten-minute intervals because almost every miner has seen the previous block before finding the next one. Speed the chain up and collisions become common, orphan rates climb, and the work being thrown away is exactly the work that was securing the ledger. This is why “just make the blocks faster” was considered a dead end for two decades.

Kaspa keeps the blocks. Instead of a chain, blocks reference multiple parents and form a directed acyclic graph — a blockDAG. The consensus protocol, GHOSTDAG, then derives a single total order over every block in that graph, and every honest node derives the same order. Nothing is discarded, so raising the block rate no longer costs security. Mainnet has run at ten blocks per second, one block every 100 milliseconds, since the Crescendo hardfork on 5 May 2025.

Blue, red, and the thing everyone gets wrong

GHOSTDAG colours blocks. A block is blue when its anticone — the set of blocks that neither reference it nor are referenced by it — is narrower than the parameter k. Otherwise it is red.

Red does not mean rejected. A red block is stored, it is ordered, and its transactions settle normally. What red costs the block is its security weight and its reward. If you remember one correction from this course, make it that one: nothing in Kaspa is discarded for arriving at the same time as something else.

Confirmation is not finality

Your transaction is confirmed once it is included in a block and GHOSTDAG has fixed its place in the order — about a second on mainnet. It is not final in the sense of being impossible to reverse, because on any proof-of-work network finality is probabilistic: it grows as work accumulates behind your transaction and never technically completes.

Both directions of this confusion are dishonest. Comparing Kaspa’s confirmation time to another chain’s finality flatters Kaspa; comparing its probabilistic finality to a proof-of-stake chain’s deterministic finality without saying they are different guarantees flatters the other chain. Name the measurement you mean.

Where the coins come from

There was no premine, no presale and no foundation allocation. Every KAS in existence was mined, starting November 2021, and the early block history is public if you want to check rather than take this page’s word for it. Since May 2022 the network has been in its chromatic phase: the block reward is multiplied by 2^(-1/12) every Kaspa month, and twelve of those steps compound to exactly one half. The result is an annual halving with no cliff and no miner revenue shock — and because 2^(-1/12) is the ratio between two semitones, and the opening rate was 440 KAS per second, the schedule is literally built on the twelve-tone musical scale.

The full emission curve, scrubbable month by month →

Course reference card
ConsensusGHOSTDAG (PoW)
Block rate10 / sec
Block time100 ms
Confirmation~1 second
FinalityProbabilistic
Hash functionkHeavyHash
Supply cap28,704,035,605 KAS
PremineNone
Address prefixkaspa:
Smallest unit1 sompi = 1e-8 KAS
How to check any of this

Run rusty-kaspa and let it validate history for itself. Short of that, read the KIP for the upgrade being discussed and match it against a tagged release. Those two habits are the entire difference between knowing something about this network and having been told it.

Figure 1Why the DAG exists
SINGLE CHAIN, FAST BLOCKSorphaned — work discardedorphaned — work discardedRaise the rate and collisions rise with it.Security is what gets thrown away.BLOCKDAG, GHOSTDAG ORDERred block — still stored,still ordered, no weightEvery block is kept. A total order is derived,and every honest node derives the same one.
Schematic, not measured data. Left: a single-chain protocol at a high block rate discards simultaneous blocks, and with them the work that secured the ledger. Right: the same blocks retained, referenced by multiple parents, and placed in one order every honest node agrees on.
KAS 110 · Protocol

What it is
used for

§ 02 — foundation, 8 min

Every use below is tagged with the property of the network that makes it possible and the thing that limits it. Three are available today and boring in the best sense; three are live but young; one is still research. Anyone who describes all seven the same way is selling something.

Payments and transfers

Available today

Send KAS between self-custodied wallets, in any amount down to one sompi, without asking anyone for permission or waiting for a business day.

Enabled by

Ten blocks per second, so inclusion and ordering happen in about a second

The limit

Fast confirmation is not instant finality. For large or irreversible deliveries, wait for more work to accumulate — the same discipline you would apply on any proof-of-work chain.

Savings you control

Available today

Hold the key yourself in cold storage. No counterparty can freeze it, dilute it by decree, or fail while holding it for you.

Enabled by

A fixed supply cap of 28,704,035,605 KAS and a fair launch with no premine

The limit

Self-custody moves the risk rather than removing it. You become the backup department, and price risk is entirely separate from custody risk.

Mining

Available today

Point ASIC hardware at a pool or a solo node and get paid from block rewards plus fees, with revenue stepping down every Kaspa month.

Enabled by

kHeavyHash proof-of-work with a public difficulty target

The limit

ASICs displaced GPUs in 2023. Manufacturer hashrate and power figures are published, not measured, and electricity price decides almost everything.

Verifying it yourself

Available today

Run rusty-kaspa, let it validate history, and stop taking anyone else’s word for your balance — including this site’s numbers.

Enabled by

A prunable Rust node that runs on ordinary hardware

The limit

A wallet talking to somebody else’s node is telling them which addresses you care about. That is a privacy cost, not a security hole.

Tokens and native assets

Live but young

KRC-20 started as inscription-style data indexed off-chain by Kasplex; with native assets on L1, tokens are migrating to the base layer.

Enabled by

Covenant opcodes and native asset support on the base layer

The limit

A migration with real steps and real deadlines is exactly what impersonation scams dress themselves up as. Take instructions only from a project’s own channels.

Smart contracts and apps

Live but young

Deploy Solidity contracts to a Kaspa L2 and bridge assets across. Existing Ethereum tooling mostly works unchanged.

Enabled by

EVM-compatible Layer 2 execution settling to Kaspa

The limit

These surfaces are new and bridges are the most-exploited infrastructure category in the industry. Treat any bridged balance as at risk in a way an L1 balance is not.

Proved off-chain execution

Under construction

A design where contract state lives off the base layer while its correctness is proved back to it.

Enabled by

Zero-knowledge verification opcodes introduced by Toccata

The limit

Research and MVP work, not a platform you can deploy to today. Anyone telling you otherwise is describing a roadmap as a product.

Figure 2The stack, and where trust enters
L2Execution layersEVM environments that run contracts and settle to Kaspa. Bridges live here — and so does bridge risk.L1.5Assets and overlaysKRC-20, indexers and the migration to native L1 assets. Rules partly enforced by consensus, partly by convention.L1Base layerProof-of-work, GHOSTDAG ordering, emission, pruning, covenants. The only part that needs nobody’s permission.Trust increases as you climb. Say which layer you are talking about.
Schematic. Each layer up adds capability and adds someone to trust. When you read a claim about Kaspa, the first question is which of these three it is about.

Reading the stack honestly

Almost every confusing argument about Kaspa is two people talking about different layers. The base layer is the part that needs nobody’s permission: proof-of-work, GHOSTDAG ordering, the emission schedule, pruning, and — since the Toccata hardfork activated at DAA score 474,165,565 on 30 June 2026 — covenant opcodes, covenant IDs, zero-knowledge verification opcodes and partitioned sequencing commitments.

That made the base layer programmable. It did not deliver an app ecosystem, audited contracts or full wallet support for everything the opcodes allow. Protocol capability and ecosystem maturity are two separate claims, and treating them as one is the most common way people end up disappointed.

Above the base layer sit assets and overlays — KRC-20, the indexers, and the ongoing migration of tokens to native L1 assets. Above that sit the Layer 2 execution environments, where Solidity contracts run and bridges move value back and forth. Bridges are the most-exploited category of infrastructure in this industry, and Kaspa’s L2 surfaces are young. That is not a reason to avoid them; it is a reason to size your exposure like someone who has read the history.

What shipped, what is proposed, and the evidence for each →

CUS 201 · Custody

The department
of self-custody

§ 03 — core, 15 min

This is the only department where a mistake is permanent. A wallet does not hold coins; it holds the key that authorises moving them, and the coins are entries in a ledger thousands of nodes agree on. Everything difficult about custody is a consequence of that one fact.

What you are actually holding

Your seed phrase is a compact representation of a secret number. From it, a wallet derives a master key, and from the master key it derives an unlimited number of addresses. The derivation only runs one way: whoever has the words has every address and every coin behind them, forever, and nobody can work backwards from an address to your phrase.

Three consequences follow, and all three surprise people who are used to bank accounts:

  • There is no reset. No developer, support desk, exchange or foundation can restore a lost phrase. Not because they are unhelpful — because the protocol gives them no mechanism.
  • A copy is a compromise. Anyone who reads your phrase has equal control, immediately and permanently. There is no partial disclosure and no revoking it.
  • Sending is final. A valid address is a valid address. If you send to the wrong one, the protocol worked perfectly and the coins are gone.

Choose a temperature, not a brand

People ask which wallet is best. The question that actually matters is where the key signs. A key that only ever signs on a dedicated offline device is cold; a key sitting in a browser profile on a laptop you also use for everything else is hot. The brand on the box is downstream of that.

Most people should hold two wallets: a hot one carrying what they would carry as cash, and something colder holding the rest. Splitting like that is not paranoia, it is the same instinct that stops you walking around with your savings in your pocket.

Why an exchange balance is a different asset

If you cannot produce the seed phrase, you do not hold KAS. You hold a claim against a company, denominated in KAS. That claim can be frozen, halted or lost with the company, and none of that requires the Kaspa protocol to fail in any way. Exchanges are useful for trading. They are not custody, and the distinction is not pedantic — it is the whole reason this network exists.

The sentence that prevents most losses

Nobody legitimate will ever ask for your seed phrase. Not a developer, not a moderator, not a support agent, not a migration, not an airdrop, not a “verification step”. There is no exception and no process that requires it. Anyone who asks is stealing from you, however fluent and helpful they sound.

Custody self-test
  • ?Can you name where every copy of your seed phrase is, right now?
  • ?Have you ever restored it into a fresh install and seen the same address?
  • ?Would a house fire destroy every copy at once?
  • ?Is any copy on a device that syncs to a cloud?
  • ?Could someone who inherits your paperwork actually recover the coins?
  • ?Is the balance you keep in a hot wallet one you could afford to lose?

If any answer made you uncomfortable, fix that one before adding a single coin to the balance.

Figure 3Anatomy of a seed phrase
01 · TWELVE OR TWENTY-FOUR WORDS010203040506070809101112Chosen from a fixed word list.The order is part of the secret.Offline media only. Never a photo.one-way derivation · plus an optional passphraseMASTER KEYnever leaves the walletDERIVATION PATHaccount / change / indexkaspa:…address 0kaspa:…address 1kaspa:…address 2as many as you wantThe arrows only run left to right. Anyone with the words on the left has everything on the right,forever — and nobody can run them backwards from an address to your phrase.
Schematic. The arrows only run left to right: the words produce the addresses, and no amount of computing runs the arrows backwards. This is why the words are the whole asset.
The temperature scale

Four tiers, sorted by where the key signs

Figure 4Cold to hot, with the trade-off named
COLD · SAVINGSHOT · CUSTODIALAir-gapped signerkey never onlineHardware walletsigns, never exportsDesktop + own nodeyou administer itMobile walletalways connectedBrowser extensionsees every dAppExchange accountnot your key at allTemperature is about where the key signs, not about which brand is on the box.Most people should hold two: a hot wallet for spending, something colder for the rest.
Schematic. Position on this scale is determined by where a signature is produced and how exposed that environment is — not by price, brand or how modern the app looks.
Cold · The savings tier

Keys never touch an internet-connected general-purpose computer

Malware on your laptop can read anything your laptop can read. A cold setup makes the private key unreadable to software you did not intend to run, because the key never exists in that machine’s memory.

Use it for

The balance you would be genuinely upset to lose, and anything you do not plan to spend this month.

Do not use it for

Day-to-day spending, token interfaces, or anything that needs you to approve something quickly.

Keys liveOn a dedicated signing device or chip
What the community uses here
  • TangemHardware card

    A card-format hardware wallet — keys never leave the chip, and there is no screen or battery to fail.

    Card-based backup model differs from seed-phrase wallets; understand it before funding.

    tangem.com
  • LedgerHardware device

    Hardware custody with KAS support through the device app ecosystem, usually paired with a third-party interface.

    Confirm current KAS and KRC-20 support on Ledger's own site before buying.

    ledger.com
  • rusty-kaspa CLI walletCommand line

    Ships with the node. No interface to trust, no telemetry, no vendor. The reference for anyone who wants to verify what a wallet is really doing.

    github.com/kaspanet/rusty-kaspa
CUS 210 · Custody practicum

Cold storage,
properly

§ 04 — practicum, 12 min

Cold storage is a property of your setup, not a product you buy. Four criteria decide whether you have it, and an eight-step drill decides whether it will still work in five years when you need it and cannot remember what you did.

CRITERION 01

The signing key is generated on the device

Not generated on your computer and then copied over. If a key ever existed in a general-purpose machine’s memory, that machine is part of your threat model forever.

CRITERION 02

The key never leaves the device

The device receives an unsigned transaction and returns a signature. That is the whole protocol. Any product that exports a private key for convenience is not cold.

CRITERION 03

You can verify what you are signing on the device itself

A screen on the signer — or a card protocol you have actually read — is what stops a compromised computer from swapping the destination address after you approve it.

CRITERION 04

The backup is offline and tested

Written by hand or stamped in metal, stored somewhere a house fire cannot reach in one go, and restored at least once into a fresh install before it holds real value.

The drill · eight steps, in order

Do it before funding
  1. 01

    Buy the device from the manufacturer

    Direct from the vendor’s own site, typed by hand, never a marketplace listing, a search advert or a gift. Supply-chain tampering is rare and unrecoverable.

  2. 02

    Initialise it yourself, offline

    Generate a new seed on the device. A device that arrives with a seed phrase already printed on a card is a trap, with no exceptions.

  3. 03

    Write the phrase by hand, twice

    Paper or metal. Not a photo, not a password manager note, not a cloud document, not a message to yourself. Anything that syncs is a copy you no longer control.

  4. 04

    Decide about a passphrase deliberately

    An optional extra word creates a different wallet from the same seed. It defeats a thief who finds your paper — and it destroys your coins if you forget it. Pick one behaviour and record the decision, not the passphrase.

  5. 05

    Wipe the device and restore from the phrase

    Before it holds anything. Confirm the same first address reappears. A backup you have never restored is a hypothesis, not a backup.

  6. 06

    Fund it with a trivial amount

    Send a small amount, confirm it arrives, then send it back out. You are testing that you can spend, not only that you can receive — those are different failures.

  7. 07

    Verify the address on the device screen

    Compare the first and last several characters against what your computer is showing. Clipboard-hijacking malware substitutes addresses and it is the single most effective theft technique there is.

  8. 08

    Separate the copies, then write the instructions

    Two locations, different failure modes, neither labelled “crypto”. Then leave a plain-language note for whoever has to do this without you — an inheritance plan nobody can follow is a loss with a delay.

What the community actually uses

For KAS specifically, the cold options people reach for are the card-format and device-format hardware wallets listed in the custody tiers above, and — for anyone comfortable at a terminal — the CLI wallet that ships with rusty-kaspa, used on a machine that does nothing else.

There is no ranking here, and this page will not give you one. A hardware wallet you understand and have practised restoring beats a better-reviewed device you set up in a hurry. The ranking that matters is between tested and untested.

Two habits worth more than any device

First, verify the destination address on the signing device’s own screen, every time, for anything you would miss. That is the only step that defends against a computer that has already been compromised.

Second, write the recovery instructions down in plain language and store them separately from the phrase itself. An inheritance plan that nobody can follow is a loss with a delay on it.

Not an endorsement, and not an audit

The wallets named on this page are the ones the Kaspa community uses, listed because you will encounter them. That is not a security review, not a guarantee, and not evidence that a domain still belongs to the people who registered it. Verify every wallet against the official Kaspa channels and the project’s own repository before you put money in it — including the ones listed here.

CUS 220 · Custody

Web wallets,
extensions, and hot keys

§ 05 — core, 8 min

“Web wallet” gets used for three completely different trust models, and the difference is where the code comes from. A page re-delivers its code every time you open it. An installed extension does not. A custodial account never gave you a key at all. Sorting these out is most of the lesson.

SurfaceWhere the code comes fromWhere the keys areWhat you are trustingVerdict
Custodial web accountA company’s servers, changeable at any momentThe companyTotal. They can freeze, halt or lose the balance, and you have no key to fall back on.Not a wallet. An account.
Browser-served web walletA web server, re-delivered every single time you load the pageYour browser, usually encrypted in local storageHigh and continuous. You are trusting whoever controls that domain and its hosting today, not the code you reviewed last month. A DNS hijack or a compromised deploy is a total loss.Convenient. Small balances only, and verify the domain every time.
Browser extension walletAn installed, versioned package that only changes when it updatesExtension storage on your machine, unlocked by a passwordMeaningfully lower than a served page — the code is pinned between updates — but the extension still sees every site you connect it to, and phishing pages are built to look exactly like the real prompt.The practical choice for tokens and dApps. Keep it as a spending wallet.
Extension or mobile, paired with a hardware signerThe installed app, but the signature comes from the offline deviceThe hardware device onlyLowest of the connected options. A compromised interface can lie to you about what you are signing, which is exactly why you confirm the destination on the device screen.Best of both, if you actually read the device screen.

How to use a hot wallet without regretting it

  1. Keep the balance at an amount you would shrug at losing, and top it up from cold storage rather than holding everything hot.
  2. Use a separate hot wallet for token interfaces, L2 dApps and anything experimental. Never connect the wallet holding your savings to a site, however reputable it looks.
  3. Read every signing prompt. If you cannot tell what it authorises, the correct action is to reject it and go find out — approvals are not reversible.
  4. Reach wallets by a bookmark you created, never a search advert, a link in a reply, a QR code in a thread, or a message from anyone.
  5. Treat a browser profile as an environment, not a vault. Every extension you install can see more than you think.

KRC-20 and the migration to native assets

For anything token-related in practice you want a KRC-20-aware wallet, and the extension wallets are furthest along there. KRC-20 began as inscription-style data indexed off-chain by Kasplex rather than enforced by consensus; with native asset support now on the base layer, tokens are migrating to L1, with some requiring their own steps.

A real migration with real deadlines is precisely the situation impersonation scams are built for. Take your instructions from the project’s own channels, be suspicious of anything urgent, and remember that no legitimate migration has ever needed a seed phrase.

Threat model · attack, mechanism, defence
  • ×Fake wallet download

    A paid search advert or a lookalike domain serves a real-looking wallet that reports your seed phrase home the moment you create or import it.

    Type the domain by hand, bookmark the real one, and install from the project’s own repository or store listing.

  • ×Clipboard hijacking

    Malware watches for an address on your clipboard and replaces it with the attacker’s. You paste, glance, and send to a stranger.

    Verify the first and last characters after pasting, and confirm the address on a hardware screen for anything large.

  • ×Seed phrase in the cloud

    A photo, a note, or a password manager entry syncs your phrase to a server. One account breach later, the coins are gone with no malware involved.

    Offline media only. If it can sync, it is not a backup — it is a leak waiting for a login.

  • ×The helpful support agent

    Somebody messages you first, usually right after you post a question in public, and walks you through a “verification” that ends with your phrase or a signature.

    Nobody legitimate ever needs your seed phrase. No developer, no moderator, no migration, no airdrop, no exception.

  • ×Blind signing

    A dApp or token interface asks you to approve something you cannot read. The approval does more than you thought.

    Refuse prompts you do not understand, use a separate hot wallet with a small balance for experiments, and never connect the wallet holding your savings.

  • ×Migration and airdrop urgency

    A real event with real deadlines gives an attacker a plausible reason for you to hurry. Urgency is the payload.

    Slow down, read the project’s own channels, and remember that a genuine deadline never requires a private key.

  • ×The single point of failure

    One phrase, one location. A fire, a flood, a theft or a house move ends the story, and no attacker was ever needed.

    Two offline copies, separate locations, different failure modes, plus written instructions for the people who inherit them.

Nearly nobody loses coins to broken cryptography

They lose them to a fake download page, a phrase in a cloud note, a substituted address, or a backup nobody ever tested. The protocol is the part of this system least likely to fail you. Spend your caution where the losses actually happen.

NET 240 · Network

One transaction,
end to end

§ 06 — seminar, 6 min

Five stages, each with a different failure mode and a different thing it proves. Being able to narrate them in order is the difference between using a wallet and understanding one.

Figure 5From your signature to accumulated work
01SIGNYour key authorisesa spend, locally02BROADCASTNode relays it intothe mempool03INCLUDEDA block carries it,at 100 ms cadence04ORDEREDGHOSTDAG fixes itsplace — about 1 s05BURIEDWork piles up behindit; reversal decaysCONFIRMATION ENDS HERE · FINALITY IS THE WHOLE ARROWStage 04 is what people mean by “Kaspa confirms in about a second”. Stage 05 never technically completes —it becomes progressively more expensive to undo, which is what probabilistic finality means.
Schematic. Stage 04 is what people mean when they say Kaspa confirms in about a second. Stage 05 is finality, which is probabilistic on any proof-of-work network and never technically completes.

Reading an address and an amount

Kaspa addresses begin with kaspa: followed by a long character string, and they carry a checksum, so mistyping one character almost always produces an invalid address rather than somebody else’s. That is a safety net, not a guarantee. Always paste rather than type, and always compare the first and last several characters against what you intended — because clipboard-hijacking malware substitutes addresses, and it is the single most effective theft technique in use.

Amounts are denominated internally in sompi, one hundred-millionth of a KAS. When a wallet shows eight decimal places, that is why.

Fees, and what they are for

Fees are priced per unit of transaction weight rather than per transaction, which is why a payment with many inputs costs more than a simple one. The Toccata hardfork moved the minimum fee rate from 1 to 100 sompi per gram. In ordinary conditions this is small; under congestion, fees are the mechanism that decides ordering, and no amount of clicking changes that.

What a confirmation is evidence of

It is evidence that the network has included your transaction and agreed where it sits in the order. It is not evidence that the counterparty is honest, that the token you received is what its name claims, or that a bridged balance is backed. Those are separate questions the ledger has no opinion about.

Watch the live mainnet dashboard while you read this →

Units and identifiers
Address prefixkaspa:
1 KAS100,000,000 sompi
Fee basisPer gram of weight
Min fee rate100 sompi/gram
Block cadence100 ms
Toccata activationDAA 474,165,565
Send a test transaction first

For any new wallet, any new address, and any large payment: send a trivial amount, confirm it arrives, then send it back. It costs almost nothing and it is the only way to test that you can spend rather than merely receive.

ECO 301 · Ecosystem

The top projects,
and what to check

§ 07 — survey, 10 min

Fifteen projects you will actually meet, grouped by what they do. Each one gets a reason it matters and the specific thing to verify before you trust it — because “top” should mean load-bearing, not loudest. No tokens are listed and no prices appear anywhere on this page.

The base layer

2 entries

rusty-kaspa

L1
Node

The reference node. Every upgrade since the Rust rewrite ships here first, and running it is what makes your view of the ledger yours rather than borrowed.

Check first · Match the version you are running against the release notes for the most recent activation.

github.com/kaspanet/rusty-kaspa

Kaspa KIPs

L1
Specifications

Where protocol changes are proposed, argued over and finalised. The only place a roadmap claim can actually be checked.

Check first · If a claim about a future upgrade is not in a KIP or a tagged release, it is a hope with a date attached.

github.com/kaspanet/kips

Execution layers

2 entries

Kasplex

L2
zkEVM L2

The zkEVM L2 with an EVM-compatible RPC, a two-way L1 bridge and its own explorer — the shortest path from Solidity to shipping on Kaspa. Also the original KRC-20 indexer, which makes it central to the native-asset migration.

Check first · Understand who operates the bridge and the sequencer before you move anything you cannot lose.

kasplex.org

Igra Labs

L2
EVM L2

Full EVM compatibility without a single centralised sequencer — a different architectural bet on censorship and liveness risk.

Check first · Different trade-offs, same youth. Neither Kaspa L2 has the operational history of a mature rollup.

www.igralabs.com

Data and explorers

3 entries

api.kaspa.org

Tooling
REST API

Public REST endpoints for supply, hashrate, block reward and node health, with no key required. Every live number on this site comes from it.

Check first · A public API is a convenience, not an authority. Your own node is the authority.

api.kaspa.org/docs

kas.fyi

Tooling
Explorer

Readable address, transaction and token views — the fastest way to confirm a payment landed or inspect a token.

Check first · An explorer shows you its interpretation of the chain. Cross-check anything surprising against a second one.

kas.fyi

Kaspa Explorer

Tooling
Explorer

The community explorer for blocks, addresses and the DAG frontier, including the parallel structure you cannot see in a list view.

Check first · Watch the frontier for a minute. Seeing several blocks at the same height is the protocol working, not a bug.

explorer.kaspa.org

Wallets and custody

5 entries

Kaspium

Custody
iOS · Android

The mobile wallet most people start with: HD accounts, plain send and receive, seed phrase in your hands.

Check first · Install from the official store listing reached via the project’s own site, and keep the balance small.

kaspium.io

Kasware

Custody
Browser extension

The KRC-20-aware extension wallet, which is what token interfaces and L2 dApp connections expect.

Check first · Extension wallets see the sites you connect them to. Use a separate one from your savings.

kasware.xyz

Kaspa NG

Custody
Desktop · Web

A desktop wallet that can talk to your own node instead of a third party’s — the practical route to not leaking your address set.

Check first · Point it at your own node if you can. Otherwise you are back to trusting someone else’s index.

kaspa-ng.org

Tangem

Custody
Hardware card

Card-format hardware custody. Keys never leave the chip, and there is no battery or screen to fail.

Check first · The card backup model is not a seed-phrase model. Read how recovery works before you fund it.

tangem.com

Ledger

Custody
Hardware device

Hardware custody through an established device ecosystem, usually paired with a third-party interface for KAS.

Check first · Confirm current KAS and token support on the vendor’s own site before buying anything.

ledger.com

Knowledge and community

3 entries

KasMedia

Knowledge
Publication

Community reporting on development, including round-ups that track what actually merged rather than what was announced.

Check first · Reporting is a pointer to a source, not the source. Follow the link to the commit or the KIP.

kasmedia.com

Kaspa Discord

Knowledge
Chat

Where node operators compare notes during activations and developers answer questions in public.

Check first · Anyone who direct-messages you first is a problem, however helpful they sound.

discord.gg/kaspa

r/kaspa

Knowledge
Forum

Longer-form discussion with a reasonable signal-to-noise ratio by crypto subreddit standards.

Check first · Upvotes are not evidence. Ask for the primary source and check it yourself.

reddit.com/r/kaspa
Read this before clicking anything above

These are third-party projects. Listing one is not an endorsement, an audit, or a claim that its domain has not changed hands since this page was written. Type domains yourself where you can, cross-check against the official Kaspa channels, and remember that anything involving a bridge carries a category of risk that holding KAS on the base layer simply does not.

CRT 350 · Critical reading

The misconception
clinic

§ 08 — seminar, 6 min

Six claims that circulate constantly, each corrected precisely, each with a one-line version you can actually use in a conversation. Being the person who states these accurately buys more credibility than any amount of enthusiasm.

A method you can apply to anything

Ask three questions of any statement about this network, including every statement on this page.

  1. Is it live, modelled, or claimed? Live numbers come from a node or a public API. Modelled numbers come from a formula, which you can check. Claims come from people.
  2. Which layer is it about? Base layer, asset overlay, or Layer 2. Guarantees do not transfer upward.
  3. What would prove it wrong? If nothing could, it is not a technical claim. It is marketing wearing technical vocabulary.

Apply the same three questions to this page. If any number here cannot be traced to a live source or a formula you can rerun, treat it as suspect and go check the primary source.

The two sources that settle arguments

A KIP tells you what a change actually specifies. A tagged release tells you whether it shipped. An activation DAA score tells you when it took effect. Anything about the future that is not in one of those three places is a plan, and plans are allowed to change — they are just not allowed to be described as history.

LAB 400 · Assessment

Flashcards
and the final exam

§ 09 — practicum, 10 min

Drill the vocabulary until it is boring. Recognising a term is not the same as being able to define it, and the fastest way to find out which one you have is to say the definition out loud before you flip the card.

1 of 21 seen
Deck contents · teaching order

The full glossary runs to 28 terms with longer entries and a search box.

The registrar

Four routes through the rest of the site

§ 10 — where to go next

Kaspa University is the overview. Each of these paths goes deeper into a specific part of it, using the interactive tools rather than more prose.

Complete beginner

Understand what this is before touching money

  1. 01What Kaspa is
  2. 02Drive the consensus lab
  3. 03Glossary and FAQ
Miner

Model revenue honestly before buying hardware

  1. 01Mining calculator
  2. 02The emission curve
  3. 03Network telemetry
Office hours

Nobody learns this alone

Post a question on the community signal board, or read the round-ups that track what actually merged rather than what was announced. One rule carries over from CUS 201: anyone who direct-messages you first is a problem, no matter how helpful they sound.

Set texts · primary sources

This site is independent and not affiliated with the Kaspa developers or any foundation. Where it disagrees with a primary source, the primary source is right.

KASPA UNIVERSITYVERIFY · DO NOT TRUST
Seal of the campus
KASPA UNIVERSITY
OPEN ENROLMENT · NO TUITION · NO SIGN-UP · NO PRICE PREDICTIONS
The rule
Verify. Do not trust.

Every number on this page is either live and labelled, or modelled and labelled. None of them are illustrative.

Kaspa University · open enrolment

Kaspa
University

Nine short courses across four departments: what this network is, what it is honestly good for, how to hold it without losing it, and which projects are worth your attention. No tuition, no sign-up, no price predictions, and no number on this page that is not either live and labelled or modelled and labelled.

At a glance
Courses9
Reading time~87 min total
PrerequisitesNone
TuitionFree · always
Teaching material · live from mainnet
api.kaspa.org · refreshed every 20s
Price
Live market price. This page never predicts one.
Network hashrate
The work defending every confirmation you rely on.
Block reward
KAS
Steps down by 2^(-1/12) every Kaspa month.
Supply cap
28.7BKAS
Fixed at 28,704,035,605. No premine, ever.
The syllabus

Four departments, nine courses, one rule

§ 00 — what you are signing up for

The rule is that a claim and its evidence travel together. Where something is verifiable, this page says how to verify it. Where something is modelled, it says so. Where something has not shipped, it gets no date. Read in order or jump to what you came for.

DEPT 01

Protocol

Consensus, emission, upgrades

Everything the network guarantees on its own, with no third party involved.

DEPT 02

Custody

Keys, backups, threat models

The only department where a mistake is permanent and nobody can reverse it for you.

DEPT 03

Ecosystem

L2s, tooling, data, tokens

Young, moving fast, and the part of the stack most likely to change after you read this.

DEPT 04

Critical reading

Claims, sources, comparisons

How to check a statement about Kaspa — including the statements on this page.

KAS 101 · Protocol

What Kaspa
actually is

§ 01 — foundation, 12 min

Kaspa is a proof-of-work ledger that does not throw work away. That single design decision is what lets it run at ten blocks per second while keeping the security model people trust Bitcoin for, and everything else on this page follows from it.

The lecture in one paragraph

In a single-chain protocol, two miners who find a block at the same moment produce a conflict, and the protocol resolves it by discarding one. That is an orphan. It is tolerable at ten-minute intervals because almost every miner has seen the previous block before finding the next one. Speed the chain up and collisions become common, orphan rates climb, and the work being thrown away is exactly the work that was securing the ledger. This is why “just make the blocks faster” was considered a dead end for two decades.

Kaspa keeps the blocks. Instead of a chain, blocks reference multiple parents and form a directed acyclic graph — a blockDAG. The consensus protocol, GHOSTDAG, then derives a single total order over every block in that graph, and every honest node derives the same order. Nothing is discarded, so raising the block rate no longer costs security. Mainnet has run at ten blocks per second, one block every 100 milliseconds, since the Crescendo hardfork on 5 May 2025.

Blue, red, and the thing everyone gets wrong

GHOSTDAG colours blocks. A block is blue when its anticone — the set of blocks that neither reference it nor are referenced by it — is narrower than the parameter k. Otherwise it is red.

Red does not mean rejected. A red block is stored, it is ordered, and its transactions settle normally. What red costs the block is its security weight and its reward. If you remember one correction from this course, make it that one: nothing in Kaspa is discarded for arriving at the same time as something else.

Confirmation is not finality

Your transaction is confirmed once it is included in a block and GHOSTDAG has fixed its place in the order — about a second on mainnet. It is not final in the sense of being impossible to reverse, because on any proof-of-work network finality is probabilistic: it grows as work accumulates behind your transaction and never technically completes.

Both directions of this confusion are dishonest. Comparing Kaspa’s confirmation time to another chain’s finality flatters Kaspa; comparing its probabilistic finality to a proof-of-stake chain’s deterministic finality without saying they are different guarantees flatters the other chain. Name the measurement you mean.

Where the coins come from

There was no premine, no presale and no foundation allocation. Every KAS in existence was mined, starting November 2021, and the early block history is public if you want to check rather than take this page’s word for it. Since May 2022 the network has been in its chromatic phase: the block reward is multiplied by 2^(-1/12) every Kaspa month, and twelve of those steps compound to exactly one half. The result is an annual halving with no cliff and no miner revenue shock — and because 2^(-1/12) is the ratio between two semitones, and the opening rate was 440 KAS per second, the schedule is literally built on the twelve-tone musical scale.

The full emission curve, scrubbable month by month →

Course reference card
ConsensusGHOSTDAG (PoW)
Block rate10 / sec
Block time100 ms
Confirmation~1 second
FinalityProbabilistic
Hash functionkHeavyHash
Supply cap28,704,035,605 KAS
PremineNone
Address prefixkaspa:
Smallest unit1 sompi = 1e-8 KAS
How to check any of this

Run rusty-kaspa and let it validate history for itself. Short of that, read the KIP for the upgrade being discussed and match it against a tagged release. Those two habits are the entire difference between knowing something about this network and having been told it.

Figure 1Why the DAG exists
SINGLE CHAIN, FAST BLOCKSorphaned — work discardedorphaned — work discardedRaise the rate and collisions rise with it.Security is what gets thrown away.BLOCKDAG, GHOSTDAG ORDERred block — still stored,still ordered, no weightEvery block is kept. A total order is derived,and every honest node derives the same one.
Schematic, not measured data. Left: a single-chain protocol at a high block rate discards simultaneous blocks, and with them the work that secured the ledger. Right: the same blocks retained, referenced by multiple parents, and placed in one order every honest node agrees on.
KAS 110 · Protocol

What it is
used for

§ 02 — foundation, 8 min

Every use below is tagged with the property of the network that makes it possible and the thing that limits it. Three are available today and boring in the best sense; three are live but young; one is still research. Anyone who describes all seven the same way is selling something.

Payments and transfers

Available today

Send KAS between self-custodied wallets, in any amount down to one sompi, without asking anyone for permission or waiting for a business day.

Enabled by

Ten blocks per second, so inclusion and ordering happen in about a second

The limit

Fast confirmation is not instant finality. For large or irreversible deliveries, wait for more work to accumulate — the same discipline you would apply on any proof-of-work chain.

Savings you control

Available today

Hold the key yourself in cold storage. No counterparty can freeze it, dilute it by decree, or fail while holding it for you.

Enabled by

A fixed supply cap of 28,704,035,605 KAS and a fair launch with no premine

The limit

Self-custody moves the risk rather than removing it. You become the backup department, and price risk is entirely separate from custody risk.

Mining

Available today

Point ASIC hardware at a pool or a solo node and get paid from block rewards plus fees, with revenue stepping down every Kaspa month.

Enabled by

kHeavyHash proof-of-work with a public difficulty target

The limit

ASICs displaced GPUs in 2023. Manufacturer hashrate and power figures are published, not measured, and electricity price decides almost everything.

Verifying it yourself

Available today

Run rusty-kaspa, let it validate history, and stop taking anyone else’s word for your balance — including this site’s numbers.

Enabled by

A prunable Rust node that runs on ordinary hardware

The limit

A wallet talking to somebody else’s node is telling them which addresses you care about. That is a privacy cost, not a security hole.

Tokens and native assets

Live but young

KRC-20 started as inscription-style data indexed off-chain by Kasplex; with native assets on L1, tokens are migrating to the base layer.

Enabled by

Covenant opcodes and native asset support on the base layer

The limit

A migration with real steps and real deadlines is exactly what impersonation scams dress themselves up as. Take instructions only from a project’s own channels.

Smart contracts and apps

Live but young

Deploy Solidity contracts to a Kaspa L2 and bridge assets across. Existing Ethereum tooling mostly works unchanged.

Enabled by

EVM-compatible Layer 2 execution settling to Kaspa

The limit

These surfaces are new and bridges are the most-exploited infrastructure category in the industry. Treat any bridged balance as at risk in a way an L1 balance is not.

Proved off-chain execution

Under construction

A design where contract state lives off the base layer while its correctness is proved back to it.

Enabled by

Zero-knowledge verification opcodes introduced by Toccata

The limit

Research and MVP work, not a platform you can deploy to today. Anyone telling you otherwise is describing a roadmap as a product.

Figure 2The stack, and where trust enters
L2Execution layersEVM environments that run contracts and settle to Kaspa. Bridges live here — and so does bridge risk.L1.5Assets and overlaysKRC-20, indexers and the migration to native L1 assets. Rules partly enforced by consensus, partly by convention.L1Base layerProof-of-work, GHOSTDAG ordering, emission, pruning, covenants. The only part that needs nobody’s permission.Trust increases as you climb. Say which layer you are talking about.
Schematic. Each layer up adds capability and adds someone to trust. When you read a claim about Kaspa, the first question is which of these three it is about.

Reading the stack honestly

Almost every confusing argument about Kaspa is two people talking about different layers. The base layer is the part that needs nobody’s permission: proof-of-work, GHOSTDAG ordering, the emission schedule, pruning, and — since the Toccata hardfork activated at DAA score 474,165,565 on 30 June 2026 — covenant opcodes, covenant IDs, zero-knowledge verification opcodes and partitioned sequencing commitments.

That made the base layer programmable. It did not deliver an app ecosystem, audited contracts or full wallet support for everything the opcodes allow. Protocol capability and ecosystem maturity are two separate claims, and treating them as one is the most common way people end up disappointed.

Above the base layer sit assets and overlays — KRC-20, the indexers, and the ongoing migration of tokens to native L1 assets. Above that sit the Layer 2 execution environments, where Solidity contracts run and bridges move value back and forth. Bridges are the most-exploited category of infrastructure in this industry, and Kaspa’s L2 surfaces are young. That is not a reason to avoid them; it is a reason to size your exposure like someone who has read the history.

What shipped, what is proposed, and the evidence for each →

CUS 201 · Custody

The department
of self-custody

§ 03 — core, 15 min

This is the only department where a mistake is permanent. A wallet does not hold coins; it holds the key that authorises moving them, and the coins are entries in a ledger thousands of nodes agree on. Everything difficult about custody is a consequence of that one fact.

What you are actually holding

Your seed phrase is a compact representation of a secret number. From it, a wallet derives a master key, and from the master key it derives an unlimited number of addresses. The derivation only runs one way: whoever has the words has every address and every coin behind them, forever, and nobody can work backwards from an address to your phrase.

Three consequences follow, and all three surprise people who are used to bank accounts:

  • There is no reset. No developer, support desk, exchange or foundation can restore a lost phrase. Not because they are unhelpful — because the protocol gives them no mechanism.
  • A copy is a compromise. Anyone who reads your phrase has equal control, immediately and permanently. There is no partial disclosure and no revoking it.
  • Sending is final. A valid address is a valid address. If you send to the wrong one, the protocol worked perfectly and the coins are gone.

Choose a temperature, not a brand

People ask which wallet is best. The question that actually matters is where the key signs. A key that only ever signs on a dedicated offline device is cold; a key sitting in a browser profile on a laptop you also use for everything else is hot. The brand on the box is downstream of that.

Most people should hold two wallets: a hot one carrying what they would carry as cash, and something colder holding the rest. Splitting like that is not paranoia, it is the same instinct that stops you walking around with your savings in your pocket.

Why an exchange balance is a different asset

If you cannot produce the seed phrase, you do not hold KAS. You hold a claim against a company, denominated in KAS. That claim can be frozen, halted or lost with the company, and none of that requires the Kaspa protocol to fail in any way. Exchanges are useful for trading. They are not custody, and the distinction is not pedantic — it is the whole reason this network exists.

The sentence that prevents most losses

Nobody legitimate will ever ask for your seed phrase. Not a developer, not a moderator, not a support agent, not a migration, not an airdrop, not a “verification step”. There is no exception and no process that requires it. Anyone who asks is stealing from you, however fluent and helpful they sound.

Custody self-test
  • ?Can you name where every copy of your seed phrase is, right now?
  • ?Have you ever restored it into a fresh install and seen the same address?
  • ?Would a house fire destroy every copy at once?
  • ?Is any copy on a device that syncs to a cloud?
  • ?Could someone who inherits your paperwork actually recover the coins?
  • ?Is the balance you keep in a hot wallet one you could afford to lose?

If any answer made you uncomfortable, fix that one before adding a single coin to the balance.

Figure 3Anatomy of a seed phrase
01 · TWELVE OR TWENTY-FOUR WORDS010203040506070809101112Chosen from a fixed word list.The order is part of the secret.Offline media only. Never a photo.one-way derivation · plus an optional passphraseMASTER KEYnever leaves the walletDERIVATION PATHaccount / change / indexkaspa:…address 0kaspa:…address 1kaspa:…address 2as many as you wantThe arrows only run left to right. Anyone with the words on the left has everything on the right,forever — and nobody can run them backwards from an address to your phrase.
Schematic. The arrows only run left to right: the words produce the addresses, and no amount of computing runs the arrows backwards. This is why the words are the whole asset.
The temperature scale

Four tiers, sorted by where the key signs

Figure 4Cold to hot, with the trade-off named
COLD · SAVINGSHOT · CUSTODIALAir-gapped signerkey never onlineHardware walletsigns, never exportsDesktop + own nodeyou administer itMobile walletalways connectedBrowser extensionsees every dAppExchange accountnot your key at allTemperature is about where the key signs, not about which brand is on the box.Most people should hold two: a hot wallet for spending, something colder for the rest.
Schematic. Position on this scale is determined by where a signature is produced and how exposed that environment is — not by price, brand or how modern the app looks.
Cold · The savings tier

Keys never touch an internet-connected general-purpose computer

Malware on your laptop can read anything your laptop can read. A cold setup makes the private key unreadable to software you did not intend to run, because the key never exists in that machine’s memory.

Use it for

The balance you would be genuinely upset to lose, and anything you do not plan to spend this month.

Do not use it for

Day-to-day spending, token interfaces, or anything that needs you to approve something quickly.

Keys liveOn a dedicated signing device or chip
What the community uses here
  • TangemHardware card

    A card-format hardware wallet — keys never leave the chip, and there is no screen or battery to fail.

    Card-based backup model differs from seed-phrase wallets; understand it before funding.

    tangem.com
  • LedgerHardware device

    Hardware custody with KAS support through the device app ecosystem, usually paired with a third-party interface.

    Confirm current KAS and KRC-20 support on Ledger's own site before buying.

    ledger.com
  • rusty-kaspa CLI walletCommand line

    Ships with the node. No interface to trust, no telemetry, no vendor. The reference for anyone who wants to verify what a wallet is really doing.

    github.com/kaspanet/rusty-kaspa
CUS 210 · Custody practicum

Cold storage,
properly

§ 04 — practicum, 12 min

Cold storage is a property of your setup, not a product you buy. Four criteria decide whether you have it, and an eight-step drill decides whether it will still work in five years when you need it and cannot remember what you did.

CRITERION 01

The signing key is generated on the device

Not generated on your computer and then copied over. If a key ever existed in a general-purpose machine’s memory, that machine is part of your threat model forever.

CRITERION 02

The key never leaves the device

The device receives an unsigned transaction and returns a signature. That is the whole protocol. Any product that exports a private key for convenience is not cold.

CRITERION 03

You can verify what you are signing on the device itself

A screen on the signer — or a card protocol you have actually read — is what stops a compromised computer from swapping the destination address after you approve it.

CRITERION 04

The backup is offline and tested

Written by hand or stamped in metal, stored somewhere a house fire cannot reach in one go, and restored at least once into a fresh install before it holds real value.

The drill · eight steps, in order

Do it before funding
  1. 01

    Buy the device from the manufacturer

    Direct from the vendor’s own site, typed by hand, never a marketplace listing, a search advert or a gift. Supply-chain tampering is rare and unrecoverable.

  2. 02

    Initialise it yourself, offline

    Generate a new seed on the device. A device that arrives with a seed phrase already printed on a card is a trap, with no exceptions.

  3. 03

    Write the phrase by hand, twice

    Paper or metal. Not a photo, not a password manager note, not a cloud document, not a message to yourself. Anything that syncs is a copy you no longer control.

  4. 04

    Decide about a passphrase deliberately

    An optional extra word creates a different wallet from the same seed. It defeats a thief who finds your paper — and it destroys your coins if you forget it. Pick one behaviour and record the decision, not the passphrase.

  5. 05

    Wipe the device and restore from the phrase

    Before it holds anything. Confirm the same first address reappears. A backup you have never restored is a hypothesis, not a backup.

  6. 06

    Fund it with a trivial amount

    Send a small amount, confirm it arrives, then send it back out. You are testing that you can spend, not only that you can receive — those are different failures.

  7. 07

    Verify the address on the device screen

    Compare the first and last several characters against what your computer is showing. Clipboard-hijacking malware substitutes addresses and it is the single most effective theft technique there is.

  8. 08

    Separate the copies, then write the instructions

    Two locations, different failure modes, neither labelled “crypto”. Then leave a plain-language note for whoever has to do this without you — an inheritance plan nobody can follow is a loss with a delay.

What the community actually uses

For KAS specifically, the cold options people reach for are the card-format and device-format hardware wallets listed in the custody tiers above, and — for anyone comfortable at a terminal — the CLI wallet that ships with rusty-kaspa, used on a machine that does nothing else.

There is no ranking here, and this page will not give you one. A hardware wallet you understand and have practised restoring beats a better-reviewed device you set up in a hurry. The ranking that matters is between tested and untested.

Two habits worth more than any device

First, verify the destination address on the signing device’s own screen, every time, for anything you would miss. That is the only step that defends against a computer that has already been compromised.

Second, write the recovery instructions down in plain language and store them separately from the phrase itself. An inheritance plan that nobody can follow is a loss with a delay on it.

Not an endorsement, and not an audit

The wallets named on this page are the ones the Kaspa community uses, listed because you will encounter them. That is not a security review, not a guarantee, and not evidence that a domain still belongs to the people who registered it. Verify every wallet against the official Kaspa channels and the project’s own repository before you put money in it — including the ones listed here.

CUS 220 · Custody

Web wallets,
extensions, and hot keys

§ 05 — core, 8 min

“Web wallet” gets used for three completely different trust models, and the difference is where the code comes from. A page re-delivers its code every time you open it. An installed extension does not. A custodial account never gave you a key at all. Sorting these out is most of the lesson.

SurfaceWhere the code comes fromWhere the keys areWhat you are trustingVerdict
Custodial web accountA company’s servers, changeable at any momentThe companyTotal. They can freeze, halt or lose the balance, and you have no key to fall back on.Not a wallet. An account.
Browser-served web walletA web server, re-delivered every single time you load the pageYour browser, usually encrypted in local storageHigh and continuous. You are trusting whoever controls that domain and its hosting today, not the code you reviewed last month. A DNS hijack or a compromised deploy is a total loss.Convenient. Small balances only, and verify the domain every time.
Browser extension walletAn installed, versioned package that only changes when it updatesExtension storage on your machine, unlocked by a passwordMeaningfully lower than a served page — the code is pinned between updates — but the extension still sees every site you connect it to, and phishing pages are built to look exactly like the real prompt.The practical choice for tokens and dApps. Keep it as a spending wallet.
Extension or mobile, paired with a hardware signerThe installed app, but the signature comes from the offline deviceThe hardware device onlyLowest of the connected options. A compromised interface can lie to you about what you are signing, which is exactly why you confirm the destination on the device screen.Best of both, if you actually read the device screen.

How to use a hot wallet without regretting it

  1. Keep the balance at an amount you would shrug at losing, and top it up from cold storage rather than holding everything hot.
  2. Use a separate hot wallet for token interfaces, L2 dApps and anything experimental. Never connect the wallet holding your savings to a site, however reputable it looks.
  3. Read every signing prompt. If you cannot tell what it authorises, the correct action is to reject it and go find out — approvals are not reversible.
  4. Reach wallets by a bookmark you created, never a search advert, a link in a reply, a QR code in a thread, or a message from anyone.
  5. Treat a browser profile as an environment, not a vault. Every extension you install can see more than you think.

KRC-20 and the migration to native assets

For anything token-related in practice you want a KRC-20-aware wallet, and the extension wallets are furthest along there. KRC-20 began as inscription-style data indexed off-chain by Kasplex rather than enforced by consensus; with native asset support now on the base layer, tokens are migrating to L1, with some requiring their own steps.

A real migration with real deadlines is precisely the situation impersonation scams are built for. Take your instructions from the project’s own channels, be suspicious of anything urgent, and remember that no legitimate migration has ever needed a seed phrase.

Threat model · attack, mechanism, defence
  • ×Fake wallet download

    A paid search advert or a lookalike domain serves a real-looking wallet that reports your seed phrase home the moment you create or import it.

    Type the domain by hand, bookmark the real one, and install from the project’s own repository or store listing.

  • ×Clipboard hijacking

    Malware watches for an address on your clipboard and replaces it with the attacker’s. You paste, glance, and send to a stranger.

    Verify the first and last characters after pasting, and confirm the address on a hardware screen for anything large.

  • ×Seed phrase in the cloud

    A photo, a note, or a password manager entry syncs your phrase to a server. One account breach later, the coins are gone with no malware involved.

    Offline media only. If it can sync, it is not a backup — it is a leak waiting for a login.

  • ×The helpful support agent

    Somebody messages you first, usually right after you post a question in public, and walks you through a “verification” that ends with your phrase or a signature.

    Nobody legitimate ever needs your seed phrase. No developer, no moderator, no migration, no airdrop, no exception.

  • ×Blind signing

    A dApp or token interface asks you to approve something you cannot read. The approval does more than you thought.

    Refuse prompts you do not understand, use a separate hot wallet with a small balance for experiments, and never connect the wallet holding your savings.

  • ×Migration and airdrop urgency

    A real event with real deadlines gives an attacker a plausible reason for you to hurry. Urgency is the payload.

    Slow down, read the project’s own channels, and remember that a genuine deadline never requires a private key.

  • ×The single point of failure

    One phrase, one location. A fire, a flood, a theft or a house move ends the story, and no attacker was ever needed.

    Two offline copies, separate locations, different failure modes, plus written instructions for the people who inherit them.

Nearly nobody loses coins to broken cryptography

They lose them to a fake download page, a phrase in a cloud note, a substituted address, or a backup nobody ever tested. The protocol is the part of this system least likely to fail you. Spend your caution where the losses actually happen.

NET 240 · Network

One transaction,
end to end

§ 06 — seminar, 6 min

Five stages, each with a different failure mode and a different thing it proves. Being able to narrate them in order is the difference between using a wallet and understanding one.

Figure 5From your signature to accumulated work
01SIGNYour key authorisesa spend, locally02BROADCASTNode relays it intothe mempool03INCLUDEDA block carries it,at 100 ms cadence04ORDEREDGHOSTDAG fixes itsplace — about 1 s05BURIEDWork piles up behindit; reversal decaysCONFIRMATION ENDS HERE · FINALITY IS THE WHOLE ARROWStage 04 is what people mean by “Kaspa confirms in about a second”. Stage 05 never technically completes —it becomes progressively more expensive to undo, which is what probabilistic finality means.
Schematic. Stage 04 is what people mean when they say Kaspa confirms in about a second. Stage 05 is finality, which is probabilistic on any proof-of-work network and never technically completes.

Reading an address and an amount

Kaspa addresses begin with kaspa: followed by a long character string, and they carry a checksum, so mistyping one character almost always produces an invalid address rather than somebody else’s. That is a safety net, not a guarantee. Always paste rather than type, and always compare the first and last several characters against what you intended — because clipboard-hijacking malware substitutes addresses, and it is the single most effective theft technique in use.

Amounts are denominated internally in sompi, one hundred-millionth of a KAS. When a wallet shows eight decimal places, that is why.

Fees, and what they are for

Fees are priced per unit of transaction weight rather than per transaction, which is why a payment with many inputs costs more than a simple one. The Toccata hardfork moved the minimum fee rate from 1 to 100 sompi per gram. In ordinary conditions this is small; under congestion, fees are the mechanism that decides ordering, and no amount of clicking changes that.

What a confirmation is evidence of

It is evidence that the network has included your transaction and agreed where it sits in the order. It is not evidence that the counterparty is honest, that the token you received is what its name claims, or that a bridged balance is backed. Those are separate questions the ledger has no opinion about.

Watch the live mainnet dashboard while you read this →

Units and identifiers
Address prefixkaspa:
1 KAS100,000,000 sompi
Fee basisPer gram of weight
Min fee rate100 sompi/gram
Block cadence100 ms
Toccata activationDAA 474,165,565
Send a test transaction first

For any new wallet, any new address, and any large payment: send a trivial amount, confirm it arrives, then send it back. It costs almost nothing and it is the only way to test that you can spend rather than merely receive.

ECO 301 · Ecosystem

The top projects,
and what to check

§ 07 — survey, 10 min

Fifteen projects you will actually meet, grouped by what they do. Each one gets a reason it matters and the specific thing to verify before you trust it — because “top” should mean load-bearing, not loudest. No tokens are listed and no prices appear anywhere on this page.

The base layer

2 entries

rusty-kaspa

L1
Node

The reference node. Every upgrade since the Rust rewrite ships here first, and running it is what makes your view of the ledger yours rather than borrowed.

Check first · Match the version you are running against the release notes for the most recent activation.

github.com/kaspanet/rusty-kaspa

Kaspa KIPs

L1
Specifications

Where protocol changes are proposed, argued over and finalised. The only place a roadmap claim can actually be checked.

Check first · If a claim about a future upgrade is not in a KIP or a tagged release, it is a hope with a date attached.

github.com/kaspanet/kips

Execution layers

2 entries

Kasplex

L2
zkEVM L2

The zkEVM L2 with an EVM-compatible RPC, a two-way L1 bridge and its own explorer — the shortest path from Solidity to shipping on Kaspa. Also the original KRC-20 indexer, which makes it central to the native-asset migration.

Check first · Understand who operates the bridge and the sequencer before you move anything you cannot lose.

kasplex.org

Igra Labs

L2
EVM L2

Full EVM compatibility without a single centralised sequencer — a different architectural bet on censorship and liveness risk.

Check first · Different trade-offs, same youth. Neither Kaspa L2 has the operational history of a mature rollup.

www.igralabs.com

Data and explorers

3 entries

api.kaspa.org

Tooling
REST API

Public REST endpoints for supply, hashrate, block reward and node health, with no key required. Every live number on this site comes from it.

Check first · A public API is a convenience, not an authority. Your own node is the authority.

api.kaspa.org/docs

kas.fyi

Tooling
Explorer

Readable address, transaction and token views — the fastest way to confirm a payment landed or inspect a token.

Check first · An explorer shows you its interpretation of the chain. Cross-check anything surprising against a second one.

kas.fyi

Kaspa Explorer

Tooling
Explorer

The community explorer for blocks, addresses and the DAG frontier, including the parallel structure you cannot see in a list view.

Check first · Watch the frontier for a minute. Seeing several blocks at the same height is the protocol working, not a bug.

explorer.kaspa.org

Wallets and custody

5 entries

Kaspium

Custody
iOS · Android

The mobile wallet most people start with: HD accounts, plain send and receive, seed phrase in your hands.

Check first · Install from the official store listing reached via the project’s own site, and keep the balance small.

kaspium.io

Kasware

Custody
Browser extension

The KRC-20-aware extension wallet, which is what token interfaces and L2 dApp connections expect.

Check first · Extension wallets see the sites you connect them to. Use a separate one from your savings.

kasware.xyz

Kaspa NG

Custody
Desktop · Web

A desktop wallet that can talk to your own node instead of a third party’s — the practical route to not leaking your address set.

Check first · Point it at your own node if you can. Otherwise you are back to trusting someone else’s index.

kaspa-ng.org

Tangem

Custody
Hardware card

Card-format hardware custody. Keys never leave the chip, and there is no battery or screen to fail.

Check first · The card backup model is not a seed-phrase model. Read how recovery works before you fund it.

tangem.com

Ledger

Custody
Hardware device

Hardware custody through an established device ecosystem, usually paired with a third-party interface for KAS.

Check first · Confirm current KAS and token support on the vendor’s own site before buying anything.

ledger.com

Knowledge and community

3 entries

KasMedia

Knowledge
Publication

Community reporting on development, including round-ups that track what actually merged rather than what was announced.

Check first · Reporting is a pointer to a source, not the source. Follow the link to the commit or the KIP.

kasmedia.com

Kaspa Discord

Knowledge
Chat

Where node operators compare notes during activations and developers answer questions in public.

Check first · Anyone who direct-messages you first is a problem, however helpful they sound.

discord.gg/kaspa

r/kaspa

Knowledge
Forum

Longer-form discussion with a reasonable signal-to-noise ratio by crypto subreddit standards.

Check first · Upvotes are not evidence. Ask for the primary source and check it yourself.

reddit.com/r/kaspa
Read this before clicking anything above

These are third-party projects. Listing one is not an endorsement, an audit, or a claim that its domain has not changed hands since this page was written. Type domains yourself where you can, cross-check against the official Kaspa channels, and remember that anything involving a bridge carries a category of risk that holding KAS on the base layer simply does not.

CRT 350 · Critical reading

The misconception
clinic

§ 08 — seminar, 6 min

Six claims that circulate constantly, each corrected precisely, each with a one-line version you can actually use in a conversation. Being the person who states these accurately buys more credibility than any amount of enthusiasm.

A method you can apply to anything

Ask three questions of any statement about this network, including every statement on this page.

  1. Is it live, modelled, or claimed? Live numbers come from a node or a public API. Modelled numbers come from a formula, which you can check. Claims come from people.
  2. Which layer is it about? Base layer, asset overlay, or Layer 2. Guarantees do not transfer upward.
  3. What would prove it wrong? If nothing could, it is not a technical claim. It is marketing wearing technical vocabulary.

Apply the same three questions to this page. If any number here cannot be traced to a live source or a formula you can rerun, treat it as suspect and go check the primary source.

The two sources that settle arguments

A KIP tells you what a change actually specifies. A tagged release tells you whether it shipped. An activation DAA score tells you when it took effect. Anything about the future that is not in one of those three places is a plan, and plans are allowed to change — they are just not allowed to be described as history.

LAB 400 · Assessment

Flashcards
and the final exam

§ 09 — practicum, 10 min

Drill the vocabulary until it is boring. Recognising a term is not the same as being able to define it, and the fastest way to find out which one you have is to say the definition out loud before you flip the card.

1 of 21 seen
Deck contents · teaching order

The full glossary runs to 28 terms with longer entries and a search box.

The registrar

Four routes through the rest of the site

§ 10 — where to go next

Kaspa University is the overview. Each of these paths goes deeper into a specific part of it, using the interactive tools rather than more prose.

Complete beginner

Understand what this is before touching money

  1. 01What Kaspa is
  2. 02Drive the consensus lab
  3. 03Glossary and FAQ
Miner

Model revenue honestly before buying hardware

  1. 01Mining calculator
  2. 02The emission curve
  3. 03Network telemetry
Office hours

Nobody learns this alone

Post a question on the community signal board, or read the round-ups that track what actually merged rather than what was announced. One rule carries over from CUS 201: anyone who direct-messages you first is a problem, no matter how helpful they sound.

Set texts · primary sources

This site is independent and not affiliated with the Kaspa developers or any foundation. Where it disagrees with a primary source, the primary source is right.