Kaspalytics Learn is under (heavy) construction. Check back regularly!
Updated: Aug 4, 2026

Network Parameters

Kaspa mainnet consensus parameters, monetary constants, hard fork history, and default ports - the numbers the rest of Learn refers to, in one table.

Every page in Learn that names a number takes it from here. Values are read out of the rusty-kaspa consensus config and the KIPs, and reflect the Crescendo (May 2025) and Toccata (June 2026) hard forks.

Consensus

ParameterValueWhere it is explained
Target block rate10 blocks per second (100 ms/block)Mining
GHOSTDAG k124PHANTOM-GHOSTDAG
Max block parents16Block Model
Mergeset size limit248The BlockDAG
Merge depth bound36,000 blocks (~1 hour)Confirmations & Finality
Finality depth432,000 blocks (~12 hours)Confirmations & Finality
Pruning depth1,080,000 blocks (~30 hours)Pruning
Coinbase maturity1,000 blocks (~100 seconds)Blocks
Proof of work hashkHeavyHash (cSHAKE256-based)Mining

Transactions & blocks

ParameterValue
Max block mass500,000 grams compute and storage; 1,000,000 grams transient (raised from 500,000 at Toccata, allowing ~250 KB block bodies)
Max transaction massThe block limits above — a transaction only has to fit in a block
Minimum relay fee rate100 sompi/gram (raised from 1 at Toccata)
Transaction versions0 and 1; version 1 added at Toccata for covenant bindings, compute budgets, and user lanes
Signature schemesSchnorr over secp256k1 (default); ECDSA over secp256k1 also supported
Transaction sighashblake2b-256, keyed with domain TransactionSigningHash

Mass, and why it is measured in three dimensions rather than bytes, is the subject of Fees & Mass.

On the old 100,000-gram cap. Before Toccata the mempool rejected any transaction above 100,000 grams in a single dimension as non-standard. That cap was relaxed shortly before activation and no longer applies — the block-fit limits are now the only per-transaction ceiling consensus imposes.

The number still shows up in one place that matters: the SDKs’ transaction generator keeps a client-side MAXIMUM_STANDARD_TRANSACTION_MASS of 100,000 grams, which is why a large input set is still split into a chain of transactions rather than one big one. That is a wallet-side policy, not a network rule.

Monetary

ParameterValue
Base unit1 KAS = 100,000,000 sompi
Max supply~28.7 billion KAS
EmissionHalves yearly via a smooth monthly reduction of (1/2)^(1/12) (~5.6%/month) - the “chromatic” schedule
Block reward~2.45 KAS/block (~24.5 KAS/second) as of July 2026

The emission schedule is a 426-entry per-month table in the coinbase logic; the per-second rate is independent of block rate (at 10 blocks per second, each block pays a tenth of the per-second subsidy).

Max supply is empirical rather than a code constant — summing the schedule per second gives ~28.4 billion, but pre-deflationary parallel DAG blocks each paid the full subsidy, putting actual emission slightly ahead. See Emission & Supply. The MAX_SOMPI constant in rusty-kaspa is 29 billion KAS, which is a monetary-amount validation ceiling, not the supply cap.

Hard fork history

Hard forkActivatedDAA scoreHighlights
CrescendoMay 5, 2025110,165,000KIP-14: 1 → 10 blocks per second, plus KIP-4 (sampled difficulty windows), KIP-9 (storage mass), KIP-10, KIP-13 (transient mass)
ToccataJune 30, 2026474,165,565KIP-16/17/20/21 (covenants, ZK precompile, sequencing commitments); larger block bodies; higher relay fee floor

Default ports

NetworkP2PgRPCwRPC (borsh)wRPC (json)
Mainnet16111161101711018110
Testnet-1016211162101721018210
Simnet16511165101751018510
Devnet16611166101761018610

See Also: Glossary, KIPs

Kaspalytics strives to provide accurate data - our highest level of effort is given to data validation and maintenance. However, we cannot guarantee 100% accuracy. Data is subject to inaccuracies and change.

Contact | © 2026 Kaspalytics