Origin story
Kaspa began as research into faster proof-of-work ordering, moved through DAGLabs and an April 2021 testnet, then launched as a public mined network after hardware, presale, and business-model paths failed to become the launch structure.
Citable summary: Kaspa grew from PHANTOM/GHOSTDAG research into a fair-launched Proof-of-Work blockDAG. Mainnet launched in November 2021 with no premine, insider allocation, or pre-sales; Crescendo later made 10 BPS live; Toccata remains a targeted programmability hard-fork track as of May 18, 2026.
The useful thesis
The clean version is not that Kaspa was born from perfect planning. The stronger sourced version is that research, startup funding, hardware plans, DeFi-sequencing ambitions, and community pressure collided until the simplest remaining launch was also the cleanest one: publish the network and let anyone mine.
That matters because every earlier structure would have made Kaspa partly answer to something outside the protocol: a hardware distribution plan, a presale contract, a startup balance sheet, or a role as infrastructure for another app ecosystem. The fair launch did not prove future adoption, price, or technical success. It did remove the official premine, pre-sale, and insider-allocation surface from the starting line.
Research first
Kaspa's research lineage starts with the question Bitcoin leaves exposed at high block rates: what should a proof-of-work network do with honest blocks found in parallel? A single-chain system normally chooses one branch and discards the other branch's work. A blockDAG tries to keep more honest work visible, then use a rule such as GHOSTDAG to order that graph into one shared payment history.
DBLP lists Yonatan Sompolinsky and Aviv Zohar's 2018 paper, PHANTOM: A Scalable BlockDAG Protocol, as an IACR ePrint publication. Kaspa.org describes Kaspa as growing from blockDAG research that continued through SPECTRE and PHANTOM into the protocols running Kaspa today.
Earlier public interviews make the through-line sharper. A 2017 Epicenter episode presented GHOST and SPECTRE as attempts to scale Bitcoin-style Proof of Work by using DAG structure instead of wasting parallel blocks. A 2018 Rethink Trust profile described DAGLabs as focused on higher Layer One throughput and faster confirmation while preserving a trustless base-layer design.
DAGLabs and testnet
Public sources do not date DAGLabs perfectly consistently. An April 26, 2021 Investing.com launch article says DAGLabs was founded in 2017 by Yonatan Sompolinsky and Guy Corem and raised $8 million from Polychain and Accomplice. The HackerNoon interview intro says Sompolinsky founded DAGLabs in 2018 to commercialize DAG protocols. The safe claim is narrower: DAGLabs funded and organized part of the pre-mainnet path before Kaspa became a public community-mined network.
Polychain's background matters here. Polychain describes itself as an investment firm managing portfolios of blockchain assets, and the public Kaspa sources place it inside the pre-mainnet DAGLabs funding story rather than as a simple post-launch market participant. The clean framing is therefore two-sided: Kaspa had no token premine, insider allocation, or pre-sale, but it did have a VC-funded DAGLabs prehistory that shaped the hardware, mining, and fair-launch debate.
Guy Corem's April 13, 2021 testnet note called Kaspa a Golang implementation of Phantom/GHOSTDAG and a generalization of Nakamoto Consensus. The April 2021 Investing.com article records the practical testnet bundle: full node, web wallet, faucet, Katnip block explorer, graph inspector, and Kashboard. It framed the project as a testnet first, with a later mainnet launch planned without pre-mining or founder allocations.
Use source-backed implementation language here. Yonatan's Hashdag archive later describes the original Kaspad codebase as an adaptation of the Bitcoin client btcd, written in Golang. That is the safer public wording than repeating unsourced "Bitcoin Core 0.19" claims.
Could-have-been paths
Hashdag's 2020 community-launch archive said Kaspa would have no premine or founder rewards, but it did not present that plan as a pure fair launch. It described DAGLabs as a for-profit miner, a pre-launch ASIC-customization path, and a DeFi-contract auction for rights to future Kaspa coins. Yonatan later said the hardware and ASIC-presale path did not materialize because optical ASIC hardware was not mature.
The April 2021 launch article framed Kaspa as faster ordering infrastructure for DeFi applications using Ethereum. The later Uphold interview recap keeps the same deeper theme: Kaspa's core specialization is sequencing, especially where finance is sensitive to transaction order and MEV. That context explains the "base sequencing layer for another ecosystem" idea without turning it into a claim that Kaspa ever shipped as an Ethereum L2.
Yonatan later described a gamenet attempt as flawed: closer to a testnet with incentives than a normal mainnet. The useful point is that the launch design changed under pressure before the public network found its actual shape.
In the later HackerNoon interview, Yonatan called DAGLabs a failed attempt to reconcile venture-backed and fair-launch models. He said investors encouraged launch despite no business model or ROI plan; when asked if Polychain pushed him to launch, he accepted that as one way to put it and added that Gadi also pushed him because he saw the potential.
Launch
Kaspa.org's current lore page says mainnet launched in November 2021 as a fair-launched Proof-of-Work network with no premine, insider allocation, or pre-sales. The current homepage adds the genesis-proof framing: every coin traces cryptographically back to an empty genesis. The public proof frame is simple: mining created the supply, and no official allocation table created coins for insiders.
That claim should stay precise. Yonatan later estimated that Kaspa core developers mined about 2.5% of total supply after launch. The Kaspa Wiki prehistory page puts the related DAGLabs/Polychain figure in the same range: after launch, DAGLabs mined with remaining funding on rented hardware for about five months; the mined coins were shared among investors, including Polychain, and former DAGLabs employees and advisers; and DAGLabs officially closed after that wind-down. The page estimates less than 3% of total supply, 840 million KAS, with its longer note saying probably closer to 2.5% and under 850 million KAS. That is not a premine, but it belongs in the early-miner picture. Fair launch lowers official insider-allocation risk. It does not erase early-miner advantage, mining-infrastructure asymmetry, later ASIC concentration, liquidity risk, or the need to fund development after launch.
The 2025 Bitcoin Takeover interview adds the strongest firsthand nuance: Yonatan described the launch as messy and reluctant, with the gamenet idea overtaken by miners who chose to keep mining. He also described the two-week halt as a recovery path that preserved the UTXO set through a second genesis that cryptographically pointed back to the last valid state. That makes the story less polished, but more source-backed.
Early stress
On November 23, 2021, Yonatan published "Kaspa (Black Tuesday)" after a network crash during the prior 48 hours. The post says the developers were not trying to roll back to an earlier preferred state; they were rebuilding and comparing a certainly valid UTXO commitment after a memory problem. That is the sourced version of the "two-week bug" story.
Kaspa also faced later state pressure. Kaspalytics recorded a September 2023 dust attack where the UTXO count jumped from about 8 million to 62 million. That belongs in the resilience timeline, but it should not be confused with the November 2021 launch bug.
Rust and Crescendo
Hashdag's 2022 "Kaspa where to" archive says Michael Sutton proposed a major refactor and Rust rewrite because the Golang codebase carried technical debt and was hard for new contributors to work in. Kaspa.org now summarizes that move as a full rewrite from the original Golang node into Rust, backed by a community grant.
Rusty Kaspa's repository describes the Rust implementation as a drop-in replacement for the older Golang node. Its README says the Crescendo hard fork took place on May 5, 2025, moving the network from 1 BPS to 10 BPS. The v1.0.0 release notes say the same hard fork transitioned Kaspa from 1 BPS to 10 BPS at mainnet DAA score 110,165,000.
Toccata boundary
The draft phrase "Toccata" can carry the wrong date if it is used for 10 BPS. Crescendo is the hard fork that made 10 BPS live on mainnet. Toccata is the targeted hard-fork track for covenant-based base-layer programmability, Silverscript, ZK-facing verification work, sequencing commitments, and native-asset groundwork.
As of May 18, 2026, Kaspa Explained treats Toccata as targeted, not live mainnet behavior. Testnet-10 and TN12 evidence matters, but mainnet activation still needs primary release and network evidence. Use Toccata Status before quoting Toccata as shipped.
What to say
| Topic | Use this wording | Avoid this shortcut |
|---|---|---|
| Code origin | Original Kaspad was Golang and source-backed as an adaptation of btcd. | Bitcoin Core 0.19, unless a durable source is added. |
| DAGLabs | DAGLabs funded and organized pre-mainnet work; public sources differ on 2017 versus 2018 dating. | A single exact founding date with no caveat. |
| Polychain | Polychain belongs in the VC-funded DAGLabs prehistory, not as a token premine or pre-sale allocation. | Ignoring Polychain context or treating it as proof of a premine. |
| Fair launch | No premine, insider allocation, or pre-sales; every coin came from mining, including the post-launch DAGLabs/Polychain-related early mining estimate. | DAGLabs/Polychain premine language, flawless distribution, or no early contributor mining. |
| Business failure | Hardware, presale, and startup paths failed to materialize before the vanilla fair launch. | Bankruptcy language unless a stronger source says bankruptcy. |
| Toccata | Targeted programmability hard-fork track as of May 18, 2026. | Toccata made Kaspa 10 BPS or mainnet activation already happened. |
Sources