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

Support Withdraw 0 trick in L2 ledger #1795

Open
v0d1ch opened this issue Jan 21, 2025 · 0 comments
Open

Support Withdraw 0 trick in L2 ledger #1795

v0d1ch opened this issue Jan 21, 2025 · 0 comments
Labels
💭 idea An idea or feature request

Comments

@v0d1ch
Copy link
Contributor

v0d1ch commented Jan 21, 2025

Why

This started as a user request in #1757 and we also think it would be beneficial for our users to be able to re-use the code they write for L1 on L2. It seems that a lot of people are using the withdraw 0 trick to reduce the tx execution costs and simplify the code logic so we should look into this.

What

Keep track of ledger certificates on L2

How

Currently we don't do anything on L2 ledger to maintain the state of registered stake certificates and only keep track of UTxO state

, Ledger.lsCertState = def

We could probably keep track of the certificates in the HeadState on L2 (needs grooming) and we should be explicit in our documentation that any certificate state on L2 will not/can't be enforced on L1.

@v0d1ch v0d1ch added 💭 idea An idea or feature request 💬 feature A feature on our roadmap and removed 💭 idea An idea or feature request labels Jan 21, 2025
@ch1bo ch1bo added 💭 idea An idea or feature request and removed 💬 feature A feature on our roadmap labels Jan 21, 2025
@ch1bo ch1bo changed the title Enable and track stake certificate registrations on L2 ledger Enable Withdraw 0 trick in L2 ledger Jan 21, 2025
@ch1bo ch1bo changed the title Enable Withdraw 0 trick in L2 ledger Support Withdraw 0 trick in L2 ledger Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💭 idea An idea or feature request
Projects
None yet
Development

No branches or pull requests

2 participants