-
Notifications
You must be signed in to change notification settings - Fork 13
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: removes syncers for aggkit migration #256
base: feat/aggkit-repo-migration
Are you sure you want to change the base?
Conversation
79c94e2
to
04b8363
Compare
d814581
to
ac8d966
Compare
@@ -276,16 +276,6 @@ RetryAfterErrorPeriod = "1s" | |||
MaxRetryAttemptsAfterError = -1 | |||
WaitForNewBlocksPeriod = "3s" | |||
|
|||
[LastGERSync] |
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.
I think we need to discuss about the config we will leave in the cdk
repo on the office hours. Maybe it makes sense to remove bunch of stuff.
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.
If we run the bridge service from the CDK, we would need to revert this change and include the LastGERSync
configuration.
rpc/bridge.go
Outdated
"github.com/0xPolygon/cdk/rpc/types" | ||
tree "github.com/0xPolygon/cdk/tree/types" | ||
"github.com/agglayer/aggkit/claimsponsor" |
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.
This might be one more topic to discuss. Should bridge rpc endpoints be left in the cdk
or in the aggkit
repo.
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.
i think bridge rpc endpoints should be on aggkit but yeah we can discuss this
baa4aaa
to
7116e38
Compare
Should we reuse the following packages from the
|
* remove aggoracle component * improve Rust build perf and cleanup * handle error when unmarashaling versions.json
* remove aggsender component * fix: remove build-tools
* mockery generate * Update .mockery.yaml Co-authored-by: Stefan Negovanović <[email protected]> * review comments * review comment --------- Co-authored-by: Stefan Negovanović <[email protected]>
327487e
to
1cd27ec
Compare
Removed db, hex and log. For |
Just to put a reminder here: |
…etector l2 and corresponding config params)
|
Description
This PR removes syncers and other relevant packages for aggkit repo migration