-
Notifications
You must be signed in to change notification settings - Fork 168
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
Conversation
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 |
@adamewozniak this update allows validators to have a "slow start" with peggo. They won't get slashed if they are late etc...
|
I will take a look on e2e |
…into robert/gravity-update
Just saw this one. We also need to enable the Batch Confirms to be 100% safe. |
We don't enable batch confirms, only Valset related messages. |
Closes: #1402
Description
In this update, Gravity Bridge
MsgValsetConfirm
andMsgValsetUpdatedClaim
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