Origin story

Kaspa's fair launch was the path left after the other paths failed

Kaspa's launch structure was not chosen. It was what remained after research into faster proof-of-work ordering ran through DAGLabs, an April 2021 testnet, and a hardware plan, a presale, and a DeFi-infrastructure pitch that each collapsed in turn.

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 is gated by DAA score 474,165,565.

Launch thesis

The origin story is a constraint story

Research, startup funding, hardware plans, DeFi-sequencing ambitions, and community pressure collided for four years before the remaining path narrowed to one option: publish the network and let anyone mine.

Every earlier structure would have made Kaspa answer to something outside the protocol: a hardware distribution deal, a presale contract, a startup balance sheet, or a supporting role inside someone else's app ecosystem. The fair launch proved nothing about future adoption, price, or technical success. What it did was remove the premine, the pre-sale, and the insider-allocation table from the starting line.

Research first

The problem came before the coin

Bitcoin at high block rates has one weak point: two honest miners can solve a block seconds apart, and the single-chain rule throws one of those blocks' work away. Kaspa's research lineage starts from that exact waste. A blockDAG keeps both blocks visible instead of discarding one, then uses a rule like GHOSTDAG to order the resulting 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 traces Kaspa's lineage through the same blockDAG research line: SPECTRE, then PHANTOM, then the protocols running Kaspa today.

Earlier interviews sharpen the through-line. A 2017 Epicenter episode presents GHOST and SPECTRE as attempts to scale Bitcoin-style Proof of Work with DAG structure instead of wasted parallel blocks. A 2018 Rethink Trust interview frames the same work around Layer One throughput, faster confirmation, and trustless base-layer design.

DAGLabs and testnet

The startup path existed before the fair launch

Public sources disagree on when DAGLabs was founded. An April 26, 2021 Investing.com launch article says 2017, by Yonatan Sompolinsky and Guy Corem, with $8 million raised from Polychain and Accomplice. The HackerNoon interview intro says Sompolinsky founded DAGLabs in 2018 to commercialize DAG protocols. Both sources are public; they don't agree. The claim that holds up either way: DAGLabs funded and organized part of the pre-mainnet path before Kaspa became a public, community-mined network.

Polychain belongs in the pre-mainnet DAGLabs funding story, and the framing cuts both ways. Kaspa had no token premine, insider allocation, or pre-sale. It also had a VC-funded DAGLabs prehistory that shaped the hardware, mining, and fair-launch debate before mainnet existed.

Guy Corem's April 13, 2021 testnet note calls Kaspa a Golang implementation of Phantom/GHOSTDAG and a generalization of Nakamoto Consensus. The April 2021 Investing.com article lists the testnet bundle: full node, web wallet, faucet, Katnip block explorer, graph inspector, Kashboard. It framed the project as testnet first, mainnet later, with no pre-mining or founder allocations planned.

On the code itself, use the source-backed version. Yonatan's Hashdag archive describes the original Kaspad codebase as an adaptation of the Bitcoin client btcd, written in Golang. That holds up; the unsourced "Bitcoin Core 0.19" claim floating around does not.

Could-have-been paths

The failed plans are part of the story

ASIC and presale path

Hashdag's 2020 community-launch archive said Kaspa would have no premine or founder rewards, and in the same breath described DAGLabs as a for-profit miner running 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 never materialized: the optical ASIC hardware it depended on wasn't ready.

DeFi sequencing path

The April 2021 launch article framed Kaspa as faster ordering infrastructure for DeFi applications running on Ethereum. The later Uphold interview recap keeps the same theme underneath: Kaspa's specialization is sequencing, which matters most where transaction order and MEV move real money. That's the source for the "base sequencing layer for another ecosystem" idea. It is not a claim that Kaspa ever shipped as an Ethereum L2.

Gamenet path

Yonatan later called the gamenet attempt flawed: closer to a testnet with incentives bolted on than an actual mainnet. The launch design kept changing under pressure before the public network found the shape it has now.

Fair-launch path

In the HackerNoon interview, Yonatan called DAGLabs a failed attempt to reconcile venture-backed and fair-launch models. Investors pushed for launch despite no business model or ROI plan. Asked directly if Polychain pushed him to launch, he agreed that was one way to describe it, and added that Gadi pushed too, because he saw the potential.

Launch

The public network launched without a premine

Kaspa.org's current lore page puts mainnet launch in November 2021: a fair-launched Proof-of-Work network with no premine, insider allocation, or pre-sales. The homepage adds the genesis-proof framing: every coin traces cryptographically back to an empty genesis. Mining created the entire supply; no allocation table set coins aside for insiders.

The claim stays narrow on purpose. No premine means no official token allocation before mining started. It does not mean equal access to early mining.

Yonatan later estimated Kaspa's core developers mined about 2.5% of total supply after launch. The Kaspa Wiki prehistory page puts the related DAGLabs/Polychain estimate below 3%, roughly 840 million KAS, and says the tighter number is probably closer to 2.5% and under 850 million KAS. That's early-miner context, a separate question from whether there was a premine.

The 2025 Bitcoin Takeover interview adds firsthand texture: Yonatan described the launch as messy and reluctant, the gamenet idea overtaken by miners who simply kept mining. The two-week halt, in his account, was a recovery path that preserved the UTXO set through a second genesis pointing back to the last valid state.

Early stress

The chain had to survive real failure

On November 23, 2021, Yonatan published "Kaspa (Black Tuesday)" after a network crash in the prior 48 hours. His account: the developers were not rolling back to an earlier preferred state, they were rebuilding and comparing a certainly-valid UTXO commitment after a memory problem. That's the sourced version of what circulates as the "two-week bug" story.

A second stress test came later. Kaspalytics recorded a September 2023 dust attack where the UTXO count jumped from about 8 million to 62 million, a separate event from the November 2021 launch bug, not a sequel to it.

Rust and Crescendo

The original implementation was not the final form

Hashdag's 2022 "Kaspa where to" archive says Michael Sutton proposed a major refactor and Rust rewrite because the Golang codebase carried technical debt that made it hard for new contributors to work in. Kaspa.org now summarizes that as a full rewrite from the original Golang node into Rust, funded by a community grant.

Rusty Kaspa's repository describes the Rust implementation as a drop-in replacement for the older Golang node. Its README puts the Crescendo hard fork on May 5, 2025, moving the network from 1 BPS to 10 BPS. The v1.0.0 release notes name the exact trigger: mainnet DAA score 110,165,000.

Toccata boundary

Crescendo is live. Toccata activated separately

"Toccata" gets misapplied to 10 BPS. It shouldn't be. Crescendo is the hard fork that made 10 BPS live on mainnet. Toccata is a separate, later hard fork: base-layer programmability with covenants, Silverscript, ZK-facing verification work, sequencing commitments, and native-asset groundwork, activated at DAA score 474,165,565.

Rusty Kaspa v2.0.1 is the current Toccata release; v2.0.0 shipped the activation. Wallet support, indexer support, and real app usage on top of Toccata are still building: check Toccata Status for where each of those stands.

What to say

The careful version holds up better

TopicUseAvoid
Code originOriginal Kaspad was Golang and source-backed as an adaptation of btcd.Bitcoin Core 0.19, unless a durable source is added.
DAGLabsDAGLabs funded and organized pre-mainnet work; public sources differ on 2017 versus 2018 dating.A single exact founding date with no caveat.
PolychainPolychain belongs in the VC-funded DAGLabs prehistory. Premine and pre-sale allocation claims need separate token-allocation evidence.Ignoring Polychain context or treating it as proof of a premine.
Fair launchNo 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 failureHardware, presale, and startup paths failed to materialize before the vanilla fair launch.Bankruptcy language unless a stronger source says bankruptcy.
ToccataBase protocol activated on mainnet at DAA score 474,165,565 (Rusty Kaspa v2.0.1); wallet, indexer, and app support are separate, still-building claims.Toccata made Kaspa 10 BPS.

Sources

Sources for this origin page

  1. Kaspa.org Lore - current public summary for fair launch, research lineage, Rust rewrite, Crescendo, Toccata, DAGKnight, and roadmap framing.
  2. Kaspa.org homepage - genesis-proof framing for no premine, no hidden allocation, and fair launch.
  3. Polychain Capital homepage - Polychain's own high-level description as an investment firm for blockchain assets.
  4. Investing.com April 2021 launch article - DAGLabs, April 2021 testnet, no-premining launch intent, and DeFi sequencing context.
  5. Guy Corem testnet note - April 2021 Kaspa testnet release and Golang Phantom/GHOSTDAG implementation framing.
  6. Epicenter episode 192 - 2017 GHOST, SPECTRE, and blockDAG research context with Aviv Zohar and Yonatan Sompolinsky.
  7. Rethink Trust 2018 interview - Layer One scalability, throughput, confirmation-speed, and trustless-design framing.
  8. Uphold Institutional interview recap - sequencing, finance, MEV, Rust implementation, and ZK-oriented future-programmability framing.
  9. Hashdag raw archive - launch-plan, ASIC/presale, gamenet, Black Tuesday, and Rust-refactor context from Yonatan Sompolinsky's writing archive.
  10. Kaspa launch plan: responding to reality - post-launch community, governance, roadmap, and maintenance context.
  11. Kaspa (Black Tuesday) - November 2021 network-crash and UTXO-commitment context.
  12. Hackernoon interview with Yonatan Sompolinsky - DAGLabs, ASIC-presale path, optical ASIC immaturity, fair launch, Polychain, and Gadi context.
  13. Kaspa Wiki prehistory page - DAGLabs mining, Polychain-related distribution, and the under-3% / 840 million KAS early-miner estimate.
  14. Bitcoin Takeover S16 E41 transcript - firsthand launch nuance, gamenet, second genesis, UTXO-set preservation, and smart-contract roadmap boundaries.
  15. DBLP: PHANTOM: A Scalable BlockDAG Protocol - bibliographic record for the 2018 PHANTOM paper by Sompolinsky and Zohar.
  16. rusty-kaspa GitHub - Rust node implementation, replacement relationship to the older Golang node, and Crescendo README context.
  17. Rusty Kaspa v1.0.0 release - Crescendo mainnet release notes and 1 BPS to 10 BPS transition.
  18. Kaspalytics Week 4, 2024 - September 2023 dust-attack UTXO-count context.

Next step

Separate origin from current status

The origin story explains how Kaspa got here. The status pages explain what the network can do today, and what still needs activation evidence before it counts as more than a plan.