Skip to content

Improve protocolInfoCardano #319

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

Closed
8 tasks done
jorisdral opened this issue Aug 23, 2023 · 3 comments
Closed
8 tasks done

Improve protocolInfoCardano #319

jorisdral opened this issue Aug 23, 2023 · 3 comments
Assignees
Milestone

Comments

@jorisdral
Copy link
Contributor

jorisdral commented Aug 23, 2023

This issue lists the different steps taken towards improving the protocolInfoCardano function

@jorisdral jorisdral converted this from a draft issue Aug 23, 2023
@jorisdral jorisdral moved this from 🔖 Ready to 🏗 In progress in Consensus Team Backlog Aug 23, 2023
@amesgen
Copy link
Member

amesgen commented Sep 29, 2023

FTR: There have been some changes to protocolInfoCardano in #352 due to the new TransitionConfig concept from Ledger.

@dnadales dnadales moved this from 🏗 In progress to 🔖 Ready in Consensus Team Backlog Oct 12, 2023
@dnadales dnadales added this to the Q3 2024 milestone Jul 11, 2024
@dnadales dnadales self-assigned this Sep 30, 2024
@dnadales dnadales moved this to 🏗 In progress in Consensus Team Backlog Sep 30, 2024
@dnadales
Copy link
Member

dnadales commented Oct 4, 2024

@amesgen, when you have time, we should discuss the remaining item in this issue and whether we can close it, as I don't see a sensible renaming.

@dnadales
Copy link
Member

dnadales commented Oct 7, 2024

As discussed out-of-band with @amesgen, with 1224, creating a separate type is no longer necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants