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

feat(warp): warp sync #417

Open
1 task done
Tracked by #419
Trantorian1 opened this issue Dec 11, 2024 · 0 comments
Open
1 task done
Tracked by #419

feat(warp): warp sync #417

Trantorian1 opened this issue Dec 11, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request exploration help wanted Extra attention is needed

Comments

@Trantorian1
Copy link
Collaborator

Is there an existing issue?

  • I have searched the existing issues

Motivation

Current l2 is mostly compute-bound by the time it take to calculate the state root of a block. This is necessary once we have reached the tip of the chain but not while we are synchronizing.

Request

Improve L2 sync times.

Solution

Add a cli option --warp-sync which computes the state root only at the end of synchronization. This has the advantage that blocks can be synchronized much faster, at the cost that any invalid/malicious information will only be detected once we have reached the tip of the chain.

This should also be applied to #393 during warp updates as we are synchronizing from a trusted source anyway.

Are you willing to help with this request?

Yes!

@Trantorian1 Trantorian1 added enhancement New feature or request help wanted Extra attention is needed labels Dec 11, 2024
@Trantorian1 Trantorian1 self-assigned this Dec 11, 2024
@Trantorian1 Trantorian1 moved this to Ready in Madara Dec 11, 2024
@Trantorian1 Trantorian1 changed the title feat(warp): Warp Sync feat(warp): warp sync Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request exploration help wanted Extra attention is needed
Projects
Status: Ready
Development

No branches or pull requests

1 participant