Skip to content

Commit d86cdfc

Browse files
oduamehoduameh
authored
Update ledger-eras.md
1 parent a7c96da commit d86cdfc

File tree

1 file changed

+66
-17
lines changed

1 file changed

+66
-17
lines changed

‎content/article/ledger-eras.md‎

Lines changed: 66 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -24,23 +24,72 @@ When new functionality needs to be introduced to Cardano, the ledger undergoes a
2424

2525
## Development phases and ledger eras
2626

27-
| Development phase | Focus | Ledger era(s) and functionality introduced | Upgrade names (examples) |
28-
| --- | --- | --- | --- |
29-
| **Byron** | Foundational layer | Byron ledger era: ada transactions, Daedalus and Yoroi wallets, federated consensus | Byron hard fork |
30-
| **Shelley** | Decentralization | Shelley ledger: stake pools, delegation, community-led block production | Shelley hard fork |
31-
| **Goguen** | Smart contracts | * Allegra: token locking
32-
33-
* Mary: native tokens and multi-asset support
34-
35-
* Alonzo: Plutus smart contracts | Allegra, Mary, and Alonzo hard forks |
36-
| **Basho** | Scalability and efficiency | Babbage ledger era: reference scripts, inline datums, reference inputs | Known as the Vasil upgrade |
37-
| **Voltaire** | Governance | Conway ledger era: on-chain governance via [CIP-1694](https://cips.cardano.org/cips/cip1694)
38-
* **Chang upgrade**: initiated Conway ledger era and introduced the first set of on-chain governance capabilities
39-
40-
* **Plomin upgrade**: extended Conway by enabling the full set of governance actions and decentralized representatives (DReps) on mainnet (epoch 537, protocol version 10.0) | Chang and Plomin upgrades |
41-
| **Future** | Ongoing roadmap | * **Dijkstra** (planned): Plutus v4, consensus and ledger integration, Conway refactors for transition
42-
43-
* **Euler** (planned): scope TBD | Next hard fork name TBD |
27+
<table style="border-collapse:collapse; width:100%;">
28+
<thead>
29+
<tr>
30+
<th style="border:1px solid #d9d9d9; padding:8px; text-align:left; vertical-align:top;">Development phase</th>
31+
<th style="border:1px solid #d9d9d9; padding:8px; text-align:left; vertical-align:top;">Focus</th>
32+
<th style="border:1px solid #d9d9d9; padding:8px; text-align:left; vertical-align:top;">Ledger era(s) and functionality introduced</th>
33+
<th style="border:1px solid #d9d9d9; padding:8px; text-align:left; vertical-align:top;">Upgrade names (examples)</th>
34+
</tr>
35+
</thead>
36+
<tbody>
37+
<tr>
38+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;"><b>Byron</b></td>
39+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Foundational layer</td>
40+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Byron ledger era: ada transactions, Daedalus and Yoroi wallets, federated consensus</td>
41+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Byron hard fork</td>
42+
</tr>
43+
<tr>
44+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;"><b>Shelley</b></td>
45+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Decentralization</td>
46+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Shelley ledger: stake pools, delegation, community-led block production</td>
47+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Shelley hard fork</td>
48+
</tr>
49+
<tr>
50+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;"><b>Goguen</b></td>
51+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Smart contracts</td>
52+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">
53+
<ul style="margin:0 0 0 1.25em; padding:0;">
54+
<li>Allegra: token locking</li>
55+
<li>Mary: native tokens and multi-asset support</li>
56+
<li>Alonzo: Plutus smart contracts</li>
57+
</ul>
58+
</td>
59+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Allegra, Mary, and Alonzo hard forks</td>
60+
</tr>
61+
<tr>
62+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;"><b>Basho</b></td>
63+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Scalability and efficiency</td>
64+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Babbage ledger era: reference scripts, inline datums, reference inputs</td>
65+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Known as the Vasil upgrade</td>
66+
</tr>
67+
<tr>
68+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;"><b>Voltaire</b></td>
69+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Governance</td>
70+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">
71+
Conway ledger era: on-chain governance via
72+
<a href="https://cips.cardano.org/cips/cip1694">CIP-1694</a>
73+
<ul style="margin:0.5em 0 0 1.25em; padding:0;">
74+
<li><b>Chang upgrade</b>: initiated Conway ledger era and introduced the first set of on-chain governance capabilities</li>
75+
<li><b>Plomin upgrade</b>: extended Conway by enabling the full set of governance actions and decentralized representatives (DReps) on mainnet (epoch 537, protocol version 10.0)</li>
76+
</ul>
77+
</td>
78+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Chang and Plomin upgrades</td>
79+
</tr>
80+
<tr>
81+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;"><b>Future</b></td>
82+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Ongoing roadmap</td>
83+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">
84+
<ul style="margin:0 0 0 1.25em; padding:0;">
85+
<li><b>Dijkstra</b> (planned): Plutus v4, consensus and ledger integration, Conway refactors for transition</li>
86+
<li><b>Euler</b> (planned): scope TBD</li>
87+
</ul>
88+
</td>
89+
<td style="border:1px solid #d9d9d9; padding:8px; vertical-align:top;">Next hard fork name TBD</td>
90+
</tr>
91+
</tbody>
92+
</table>
4493

4594
**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.
4695

0 commit comments

Comments
 (0)