Skip to content

[EC Api] - Ledger eras #1610

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 2, 2025
Merged

[EC Api] - Ledger eras #1610

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0557c92
[EC Api] - Added: Ledger eras
Oct 2, 2025
5d82433
Update ledger-eras.md
oduameh Oct 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions content/article/ledger-eras.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,13 +25,13 @@ When new functionality needs to be introduced to Cardano, the ledger undergoes a
## Development phases and ledger eras

| Development phase | Focus | Ledger era(s) and functionality introduced | Upgrade names (examples) |
| :---- | :---- | :---- | :---- |
| --- | --- | --- | --- |
| **Byron** | Foundational layer | Byron ledger era: ada transactions, Daedalus and Yoroi wallets, federated consensus | Byron hard fork |
| **Shelley** | Decentralization | Shelley ledger: stake pools, delegation, community-led block production | Shelley hard fork |
| **Goguen** | Smart contracts | Allegra: token locking Mary: native tokens and multi-asset support Alonzo: Plutus smart contracts | Allegra, Mary, and Alonzo hard forks |
| **Goguen** | Smart contracts | Allegra: token locking Mary: native tokens and multi-asset support Alonzo: Plutus smart contracts | Allegra, Mary, and Alonzo hard forks |
| **Basho** | Scalability and efficiency | Babbage ledger era: reference scripts, inline datums, reference inputs | Known as the Vasil upgrade |
| **Voltaire** | Governance | Conway ledger era: on-chain governance via [CIP-1694](https://cips.cardano.org/cips/cip1694) | Chang and Plomin upgrades The Chang upgrade initiated the Conway ledger era and introduced the first set of on-chain governance capabilities The Plomin upgrade extended Conway by enabling the full set of governance actions and decentralized representatives (DReps) on mainnet (epoch 537, protocol version 10.0). |
| **Future** | Ongoing roadmap | **Dijkstra** (planned): Plutus v4, consensus and ledger integration, Conway refactors for transition **Euler** (planned): scope TBD | Next hard fork name TBD |
| **Voltaire** | Governance | Conway ledger era: on-chain governance via [CIP-1694](https://cips.cardano.org/cips/cip1694) | Chang and Plomin upgrades The Chang upgrade initiated the Conway ledger era and introduced the first set of on-chain governance capabilities The Plomin upgrade extended Conway by enabling the full set of governance actions and decentralized representatives (DReps) on mainnet (epoch 537, protocol version 10.0). |
| **Future** | Ongoing roadmap | **Dijkstra** (planned): Plutus v4, consensus and ledger integration, Conway refactors for transition **Euler** (planned): scope TBD | Next hard fork name TBD |

**Hard fork upgrades** use distinct names for community communication (for example, Chang → Plomin). These names are always mapped internally to a ledger era and protocol version. Hard forks activate a ledger era and may also introduce additional intra-era changes.

Expand Down
Loading