morty/permissionless batches recovery#1639
morty/permissionless batches recovery#1639jonastheis merged 144 commits intojt/permissionless-batches-recoveryfrom
Conversation
This reverts commit fe6451b.
| Run with `make cloud_prover`. | ||
|
|
||
| This will prove chunks, the batch and bundle. | ||
| Run `make check_proving_status` |
There was a problem hiding this comment.
Maybe not related to this PR, but do we have some docs for the next step? e.g., withdraw the funds in L1. If any, it's nice to have it placed here.
There was a problem hiding this comment.
yeah there should be some more extended docs on how to do this from beginning to end
There was a problem hiding this comment.
Good suggestion, @jonastheis Do you want me to add those steps? Or you will do it later.
There was a problem hiding this comment.
https://github.com/scroll-tech/scroll-bridge-sdk
A convenient tool for users to get withdraw proof.
…onless-batches-recovery
jonastheis
left a comment
jonastheis
left a comment
There was a problem hiding this comment.
can you check the failing CI? it seems to pass in the base branch
| Run with `make cloud_prover`. | ||
|
|
||
| This will prove chunks, the batch and bundle. | ||
| Run `make check_proving_status` |
There was a problem hiding this comment.
yeah there should be some more extended docs on how to do this from beginning to end
|
The prover/coordinator version is still 0.2.0, will update to 0.3.0. |
…onless-batches-recovery
…b.com/scroll-tech/scroll into morty/permissionless-batches-recovery
jonastheis
merged commit 9d09283
into
jt/permissionless-batches-recovery
10 participants
Purpose or design rationale of this PR
Describe your change. Make sure to answer these three questions: What does this PR do? Why does it do it? How does it do it?
Add coordinator and prover to support permissionless batches.
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
Deployment tag versioning
Has
tagincommon/version.gobeen updated or have you addedbump-versionlabel to this PR?Breaking change label
Does this PR have the
breaking-changelabel?