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

chore: bump Gravity-Bridge #1412

Merged
merged 8 commits into from
Sep 19, 2022
Merged

chore: bump Gravity-Bridge #1412

merged 8 commits into from
Sep 19, 2022

Conversation

robert-zaremba
Copy link
Member

@robert-zaremba robert-zaremba commented Sep 18, 2022

Closes: #1402

Description

In this update, Gravity Bridge MsgValsetConfirm and MsgValsetUpdatedClaim is active, and validators must update the validator set in Ethereum smart contract to fully enable Gravity Bridge and not get slashed.
This is the first step to fully enable Gravity Bridge, after we disabled it in v1.1.x

@robert-zaremba robert-zaremba added this to the v3 milestone Sep 18, 2022
@robert-zaremba robert-zaremba requested review from a team as code owners September 18, 2022 20:52
@adamewozniak
Copy link
Collaborator

can we keep this post-v3? I don't see why validators should have to start price feeders and also deal with peggo at the same time. Let's stagger it and make it easier for ourselves
cc: @RafilxTenfen / @facundomedica

@robert-zaremba
Copy link
Member Author

@adamewozniak this update allows validators to have a "slow start" with peggo. They won't get slashed if they are late etc...
We need this update because:

  • we need to enable GB sooner than later
  • this will allow us to test the status of valset in GB contract.

@robert-zaremba robert-zaremba removed this from the v3 milestone Sep 18, 2022
@RafilxTenfen
Copy link
Contributor

I will take a look on e2e

@adamewozniak adamewozniak merged commit fea1e4c into main Sep 19, 2022
@adamewozniak adamewozniak deleted the robert/gravity-update branch September 19, 2022 02:30
@facundomedica
Copy link
Contributor

Just saw this one. We also need to enable the Batch Confirms to be 100% safe.
BTW MsgValsetUpdatedClaim is not necessary to avoid slashes (the Umee chain doesn't care if the ETH valset is up to date)

@robert-zaremba
Copy link
Member Author

We don't enable batch confirms, only Valset related messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

re-enable ValsetConfirm Gravity Bridge.
4 participants