-
Notifications
You must be signed in to change notification settings - Fork 7
[2/2] Decouple ETH Bridge from signal service #113
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
Conversation
height --> index
fix fix test fix test
0cb33a0
to
6626f47
Compare
fix fix test fix test single
6626f47
to
290de34
Compare
The previous comment was ambiguous about whether we support full state roots. I think `StateProofNotSupported` as an error is unclear, and might actually state the opposite of the error. For context - the `LibSignal` library attempts to prove a storage location inside a root. - we expect this to be a state root. The proof is multi-step: first prove the account's storage root within the state proof, then prove the storage location against the storage root. - the library also supports skipping step 1 and treating the root as a storage root directly. The signal service does not. At some point we will have to generalise the commitment and storage proof mechanism to support block hashes as commitments (which is natural for rollups) and arbitrary state for appchains. In the mean time we are being opinionated that the commitment is a state root.
comment comment better error comment
7645b16
to
7448d95
Compare
Changes to gas cost
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! My only big question is if we should use the same address for the EthBridge on both chains or keep the counterpart
variable.
I also complete the TODO by making claimDeposit
nonReentrant using transient storage
Co-authored-by: Gustavo Gonzalez <[email protected]>
…-rollup into decouple-eth-bridge
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I haven't reviewed the tests, but I think we can start merging these PRs and I'll take a look at tests before we merge the big one into main
PR solves: