-
Notifications
You must be signed in to change notification settings - Fork 88
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.
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
Switch L2 ledger to Conway #1178
Milestone
Comments
ch1bo
added
💬 feature
A feature on our roadmap
and removed
💭 idea
An idea or feature request
labels
Jan 19, 2024
4 tasks
ch1bo
added
green 💚
Low complexity or well understood feature
and removed
amber ⚠️
Medium complexity or partly unclear feature
labels
Jul 9, 2024
When is the right time to merge this? |
When mainnet completes the fork to Conway. When that happens, let's merge! |
github-project-automation
bot
moved this from In Progress 🕐
to Done ✔
in ☕ Hydra Team Work
Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why
While the Cardano node needs to be able to maintain support to all past eras (to verify the full chain), a Hydra head has a definite beginning and end of existence.
As maintainers of a
hydra-node
, we want to drop support for old eras to improve maintainability.The next hard-fork event will be the fork into
Conway
era in Q1 or Q2 2024.After #1177, we want to drop support for
Babbage
eventually.What
A new version of
hydra-node
which requires aConway
network is created.The
hydra-node
does detect and inform users when the network is still inBabbage
era.The layer 2 ledger does understand
Conway
transactions (i.e. this includesPlutusV3
scripts)How
Conway
transactions.PlutusV3
as well heretype Era
alias, but just point it toConwayEra
The text was updated successfully, but these errors were encountered: