Skip to main content

Cardano network upgrades

What the next hard fork changes and how far along it is.

Upcoming

Dijkstra, phase 1

  • Protocol version 12
Developer testnet13 changes
  1. In development
  2. Developer testnet
  3. Preview testnet
  4. Preprod testnet
  5. On-chain vote
  6. Mainnet

The hard fork plan targets code completion for Q4 2026. The hard fork working group reports in its minutes that everything except Linear Leios and fair minimum fees can be tested on DijkstraNet, a test network for developers.

  • Ouroboros Linear LeiosA block producer can publish a second, larger block alongside the regular one. Its transactions enter the ledger after a committee of stake pools votes for it, so the network carries more transactions.
  • Nested transactionsA transaction can contain sub-transactions that settle together, so a swap offer can be made and accepted without an exchange in between.
  • Guard scriptsA new script type can check a transaction without spending or minting.
  • Account addresses, phase 1Ada can be deposited into account addresses, which today only receive staking rewards.
  • isValid removed from transactionsRemoving the field simplifies the transaction structure and script execution.
  • Block body formatA block stores each transaction in one piece, which Leios needs.
  • Plutus V4A new script context lets smart contracts read the transaction and ledger structures that Dijkstra introduces.
  • Fees for reference inputsThe fee function accounts for reference inputs.
  • Reference script pricing and limitsThe pricing and size limits of reference scripts have been fixed values since Conway. They become protocol parameters, which governance can change once the Constitution and its guardrails cover them.
  • Reward withdrawals without a DRepAda holders can withdraw their rewards without first delegating their vote to a DRep.
  • Pledge leverage parameterA new parameter can tie stake pool rewards to pledge. It starts switched off, so nothing changes at the hard fork.
  • Groundwork for PerasPhase 1 adds the block format and parameters Peras needs, without switching Peras on.
  • Fair minimum feesA new parameter sets a minimum stake pool margin, which reward calculation applies when a pool's own margin is lower. It starts at zero, and governance can raise it later.

Dijkstra, phase 2

In developmentOuroboros Peras
  1. In development
  2. Developer testnet
  3. Preview testnet
  4. Preprod testnet
  5. On-chain vote
  6. Mainnet

The hard fork plan targets code completion for Q2 2027.

  • Ouroboros PerasIn each round a committee of stake pools votes for a recent block. A block with enough votes is far less likely to be rolled back, so transactions settle sooner.

Completed

van Rossem

  • Protocol version 11
  • Conway Era
July 18, 2026

Intra-era upgrade delivering cleaner ledger rules, VRF key uniqueness, Plutus smart contract performance improvements and new cryptographic built-ins.

  • Built-in functions in every Plutus versionPlutus V1 and V2 scripts can use the built-in functions that only newer Plutus versions had.
  • Case expressions on built-in typesScripts can use case expressions on Bool, Integer, and Data values, which makes matching on data faster.
  • Array typeA built-in array type lets a script look up an element in constant time.
  • Multi-asset value typeScripts can work with multi-asset values directly, without encoding them as nested maps.
  • Modular exponentiationA built-in function calculates modular exponentiation, including inverses.
  • dropListA built-in function drops a given number of elements from a list, which makes reading an element by its position much faster.
  • Multi-scalar multiplicationA built-in function computes multi-scalar multiplication over the BLS12-381 curve, an operation that cryptographic protocols use.
  • VRF key uniquenessNo two stake pools can register the same VRF key. The ledger enforces this from the hard fork on.
  • Constitutional Committee voting ruleA restriction on Constitutional Committee votes was only checked when a node received a transaction. It is now a ledger rule.
Epoch
644
Transaction ID
fdd468da5cc4ac8431dcd7e2b3211666c73bc229f85879469f67f1d9d51d344d

Plomin

  • Protocol version 10
  • Conway Era
January 29, 2025

Ended the bootstrap phase of CIP-1694. DReps vote on every type of governance action, and treasury withdrawals, constitution updates, no-confidence motions and changes to the Constitutional Committee became possible.

  • Reward withdrawals need a DRepWith the bootstrap phase over, staking rewards can only be withdrawn when the stake is delegated to a DRep or to one of the options Abstain and No confidence.
  • Logical operations on byte stringsPlutus V3 scripts get built-in functions for AND, OR, XOR, and complement on byte strings, and for reading and setting single bits.
  • Bit shifts and rotationsPlutus V3 scripts get built-in functions that shift and rotate byte strings, count the set bits, and find the first set bit.
  • RIPEMD-160 hashingA built-in function computes the RIPEMD-160 hash, for compatibility with Bitcoin's cryptography.
Epoch
537
Transaction ID
0b19476e40bbbb5e1e8ce153523762e2b6859e7ecacbaf06eae0ee6a447e79b9

Chang

  • Protocol version 9
  • Conway Era
September 1, 2024

Introduced the first batch of decentralized governance features of CIP-1694. During this bootstrap phase only parameter changes, hard fork initiations and info actions were possible, and DReps voted on info actions only.

  • On-chain governanceAny ada holder can submit a governance action. A Constitutional Committee, DReps, and stake pool operators vote on them.
  • Plutus V3A new Plutus version whose scripts can also validate governance actions and votes.
  • Sums of productsPlutus Core supports data types natively, which makes scripts more efficient.
  • BLS12-381 built-insBuilt-in functions for operations on the BLS12-381 curve, which many cryptographic schemes build on.
  • Keccak-256 hashingA built-in function computes the Keccak-256 hash, for compatibility with Ethereum's cryptography.
  • Integer and byte string conversionsBuilt-in functions convert an integer to a byte string and back.
  • Uniform script argumentsEvery Plutus V3 script takes the same single argument, whatever it validates, and a spending script no longer needs a datum.
  • Reference scripts for Plutus V1A transaction that runs a Plutus V1 script can point to the script on the chain and no longer has to carry it, which saves block space.
Epoch
507
Transaction IDs
9ba6a580bceb8f94e65a683e8291c89382835f46e3cf928eb521f5581ade4820, 4e377ceb5c5721257a3d7960f3053468bbea45ed8ac22cd559c69e757da5e0ae

Valentine

  • Protocol version 8
  • Babbage Era
February 14, 2023

Intra-era upgrade that lets Plutus scripts verify signatures made on other blockchains, such as Bitcoin.

  • ECDSA and Schnorr signaturesBuilt-in functions let Plutus scripts verify ECDSA and Schnorr signatures over the secp256k1 curve.
Epoch
394
Transaction IDs
a83f479c5635e1e563a19f6e72a1be59fb082bbf31de90cc176850ee799b08ac, 62c3c13187423c47f629e6187f36fbd61a9ba1d05d101588340cfbfdf47b22d2

Vasil

  • Protocol version 7
  • Babbage Era
September 22, 2022

Improved the scalability and performance of the network, named after Vasil Dabov, a Cardano community member.

  • Reference inputsA transaction can read an output without spending it.
  • Inline datumsA datum can be attached to an output itself, where before the output only held its hash.
  • Reference scriptsA script can be attached to an output and used by other transactions, which makes those transactions much smaller.
  • Collateral outputsA transaction can name an output for the change from its collateral. Before, a failed script consumed the collateral input entirely.
  • serialiseDataA built-in function serializes data to a byte string.
Epoch
365
Transaction IDs
3abda97c78c71e8a21473529aca94d78d364dfa1a866ef8245885e18085b4e4c, 8230f33cd7ad3f8601e94ea2b18abdc591187e190ea8ebecc25e20fc66200f13

(Lobster)

  • Protocol version 6
  • Alonzo Era
October 22, 2021

Intra-era upgrade that fixed a bug in how time is converted for Plutus scripts.

Epoch
298

Alonzo

  • Protocol version 5
  • Alonzo Era
September 12, 2021

Introduced smart contract capabilities using Plutus, enabling the deployment of decentralized applications (DApps).

Epoch
290

Mary

  • Protocol version 4
  • Mary Era
March 1, 2021

Brought native token functionality to Cardano, allowing users to create and transact with custom tokens.

Epoch
251
Transaction ID
b7f5658a5aabced7f8599cf7bf7cb9d6f730b865a5a0430f2dc7488caf25752e

Allegra

  • Protocol version 3
  • Allegra Era
December 16, 2020

Added token locking capabilities, which was a prerequisite for the smart contract functionality.

Epoch
236
Transaction ID
1fbd16c1d1b1933f2f97a313db8c749bdcf65a39d996515b0f5e5535baad68e8

Shelley

  • Protocol version 2
  • Shelley Era
July 29, 2020

Introduced staking and decentralization features, transitioning from a federated to a decentralized system.

Epoch
208
Transaction ID
N/A (Transitioned through several updates)

OBFT

  • Protocol version 1
  • Byron Era
February 20, 2020

Switched consensus from Ouroboros Classic to Ouroboros BFT, the bridge to the Shelley hard fork.

Epoch
176

Byron

  • Protocol version 0
  • Byron Era
September 23, 2017

The launch of the Cardano mainnet and introduction of the ada cryptocurrency.

Epoch
0
Transaction ID
N/A (Genesis block)

About hard forks

What a hard fork is

Hard forks in Cardano do not signify division and differences within the ecosystem. On the contrary, they define a specific and collectively agreed-upon exact time (slot) when all nodes switch to new protocol rules, sometimes starting a new era, applying new functions, validation rules, or parameter values. Stake pool operators install the new node version ahead of time. Since Plomin, the switch itself is approved on chain through a hard fork governance action. A Cardano hard fork is, therefore, not a separation but a precise collective evolution.

How upgrades go live

Every upgrade since Shelley went live through the hard fork combinator while the network kept running. How an upgrade is proposed, approved through governance and rolled out is explained in how Cardano works.

Transaction IDs

Byron, the OBFT switch, Shelley, Alonzo and the Lobster upgrade are listed without a single transaction ID. Up to Chang, each ID is a protocol update proposal that triggered the hard fork. Plomin and van Rossem were approved as hard fork governance actions, and their IDs identify those actions.