-
Notifications
You must be signed in to change notification settings - Fork 341
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
Monitor v3 signal #4073
Comments
so we're currently at 34% have signalled for v3. We need 83% to signal before we submit a MsgTryUpgrade |
There is a block delay after a successful MsgTryUpgrade. Currently the delay is 50,400 block delay which is 7 days based on a 12 second block time. The observed block time on Mainnet Beta is 11.82 seconds. At the observed block rate, it will take the chain 6 days, 1 hour, and 28 minutes to produce 50,400 blocks. We want the chain to upgrade 2 - 5PM UTC so we want to submit the MsgTryUpgrade between 12:30 - 3:30PM UTC or 7:30 - 10:30AM ET. Can submit a MsgTryUpgrade via: celestia-appd tx signal try-upgrade --from key-celestia --fees 210000utia |
getting close!!
|
Submitted MsgTryUpgrade. The v3 activation height on Mainnet Beta is:
https://www.mintscan.io/celestia/block/2993219/ which is estimated at Dec 12th 2024, 11:57:02+00:00 |
Context
As of December 2nd, validators are encouraged to upgrade to the latest v3.x.x release (v3.0.2 ATM) and signal for v3
Proposal
The text was updated successfully, but these errors were encountered: