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

Write a tutorial showing how to build a custom ledger for Hydra #1809

Open
noonio opened this issue Jan 29, 2025 · 2 comments
Open

Write a tutorial showing how to build a custom ledger for Hydra #1809

noonio opened this issue Jan 29, 2025 · 2 comments
Labels
green 💚 Low complexity or well understood feature

Comments

@noonio
Copy link
Contributor

noonio commented Jan 29, 2025

  • Show which repos to fork
  • Roughly the code changes required
  • How you can test it

It doesn't need to be super-reproducible; it can point to the old PRs; but it should be enough to get someone started if they are motivated.

@noonio noonio moved this from Triage 🏥 to Later in ☕ Hydra Team Work Jan 29, 2025
@noonio noonio added the green 💚 Low complexity or well understood feature label Jan 29, 2025
@locallycompact
Copy link
Contributor

I don't think this is something we particularly want to recommend people do. Extending plutus is fragile, especially when it still informs the L1 toolchain, and we don't know the ways in which we can safely override the ledger code itself.

A better way to do this could be to maintain an L2 ledger ourselves, that extends cardano-ledger compositionally. then it's natural and safe for someone to fork that and extend it.

@noonio
Copy link
Contributor Author

noonio commented Jan 29, 2025

It's an interesting idea, and a good point.

I think the problem I have is I don't want us to take on extra work of maintaining a separate ledger; and certainly not indefinitely.

I think what I'd like is just a middle-ground between that, and what we've done so far, and having a full implementation. I more want to write a kind of experience-report-ish style document, that captures the knowledge we have gained. At a minimum it could just be some entries on the Logbook.

I.e. I don't think the tutorial needs to be super-followable; just give a guide should someone wish to do it in the future.

@noonio noonio moved this from Later to Todo 📋 in ☕ Hydra Team Work Feb 3, 2025
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
Projects
Status: Todo 📋
Status: No status
Development

No branches or pull requests

2 participants