-
Notifications
You must be signed in to change notification settings - Fork 9
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: e2e test Pesimisstic L2 to L2 claim #239
Conversation
* Simplify HashMeddler * fix: TestCertificateHeaderString UT
…t lower than in local storage (#209)
This set a limit on certificate size that can be set on config file (the size of certificate it's an estimation) There are a special situation that is going to send a certificate bigger than maximium: - [ initial_block, end_block ] -> size exceed - [ initial_block, (end_block -1) ] -> no bridges, so we have to send previous one even that exceed the maximum size MaxCertSize: max size in bytes of certificate. Default 8Mb. Currently the maximum on Agglayer is 10Mb ``` [AggSender] MaxCertSize = 8388608 ```
* fix: use hex instead of byte arrays * feat: UT * fix: change estimated certificate size * fix: UT coverage * fix: bridge exit metadata hash * fix: last sent certificate block (#234)
…agglayer (#227) * chore: update the versions.json * Remove PPError interface and use the error instead * Remove non-applicable test cases * Rename * test: increase UT coverage * test: certificate status unmarshal json * test: TestMerkleProofString * test: TestGlobalIndexString * test: move helper functions to a separate file * test: TestL1InfoTreeLeafString * test: TestClaimType * test: parallel execution, renames
…t` hash (#237) * fix: calculate correct root for LER merkle proof, and fix BridgeExit hash * fix: UTs * fix: comments
…), so it's retried
af3e06f
to
77d5fcf
Compare
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.
Generally LGTM, leaving a couple of more comments to consider.
Quality Gate passedIssues Measures |
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
Description
The PR add e2e test for L2 to L2 bridge. To do this it require several improvements:
global_index
. It needs, a RPC to get the submitted certificates and also a new tool to find theglobal_index
E2E
kurtosis-cdk
that is still on a branchclaim
only claim the specific depositRPC for aggsender
In order to be able to retrieve all certificates for verify which one contain the desired
importedBridgeExit
have create a aggsender end-point.RPC
component, you must useBRIDGE
componentAggSender.EnableRPC
aggsender_getCertificateHeaderPerHeight
: you can ask for highest certificate of an specific height.Example of usage for requesting the highest height:
aggsender_status
Tools
Add new folder
tools
:Makefile
tagetbuild-tools
aggsender_find_imported_bridge
: find out aimportedBridgeExit
in settled certificates ofaggsender
, it use RPC to retrieve certificates, also require to be able to unmarshal certificatesConfiguration changes
DryRun
: allow to prevent aggsender to submit certificatesEnableRPC
: It create a end point