Skip to content
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

Closed
2 tasks done
ch1bo opened this issue Nov 24, 2023 · 2 comments · Fixed by #1338
Closed
2 tasks done

Switch L2 ledger to Conway #1178

ch1bo opened this issue Nov 24, 2023 · 2 comments · Fixed by #1338
Assignees
Labels
green 💚 Low complexity or well understood feature 💬 feature A feature on our roadmap
Milestone

Comments

@ch1bo
Copy link
Collaborator

ch1bo commented Nov 24, 2023

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 a Conway network is created.

  • The hydra-node does detect and inform users when the network is still in Babbage era.

    • This may be just the same mechanism as described in Conway support #1177
    • Additional instructions or documentation to connect "later" when synchronized may be appropriate here.
  • The layer 2 ledger does understand Conway transactions (i.e. this includes PlutusV3 scripts)

How

  • Preparing this already prior to the hard-fork
    • would allow us to push any problems we have upstream!
    • Early adopters can use plutusv3 and conway with hydra already before the hard-for
  • Change the Hydra protocol transactions to be Conway transactions.
    • As this is a breaking change already, we might want to switch to PlutusV3 as well here
    • Keep the "fixed" type Era alias, but just point it to ConwayEra
@ch1bo ch1bo added the 💭 idea An idea or feature request label Nov 24, 2023
@ch1bo ch1bo added 💬 feature A feature on our roadmap and removed 💭 idea An idea or feature request labels Jan 19, 2024
@ch1bo ch1bo changed the title Drop Babbage support Switch L2 ledger to Conway Jan 19, 2024
@ch1bo ch1bo added the amber ⚠️ Medium complexity or partly unclear feature label Jan 23, 2024
@locallycompact locallycompact self-assigned this Feb 7, 2024
@ch1bo ch1bo linked a pull request Mar 15, 2024 that will close this issue
4 tasks
@ch1bo ch1bo added green 💚 Low complexity or well understood feature and removed amber ⚠️ Medium complexity or partly unclear feature labels Jul 9, 2024
@noonio
Copy link
Contributor

noonio commented Jul 18, 2024

When is the right time to merge this?

@ch1bo ch1bo added this to the 0.19.0 milestone Aug 13, 2024
@noonio noonio modified the milestone: 0.19.0 Aug 13, 2024
@noonio
Copy link
Contributor

noonio commented Aug 19, 2024

When is the right time to merge this?

When mainnet completes the fork to Conway.

When that happens, let's merge!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
green 💚 Low complexity or well understood feature 💬 feature A feature on our roadmap
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants