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.

Sign up for GitHub

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

Update network-upgrade-process.md #1768

Closed
wants to merge 1 commit into from
Closed

Update network-upgrade-process.md #1768

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions how-to-guides/network-upgrade-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ The upgrade process can be broken down into a few steps:
1. A new binary is released with the new features to be tested on testnets.
1. Validators upgrade their nodes to the new binary, on [Arabica devnet](./arabica-devnet.md), [Mocha testnet](./mocha-testnet.md), and finally on Celestia [Mainnet Beta](./mainnet.md).
- Upgrades using pre-programmed height (v2) activate at a predetermined block number.
- Upgrades using in-protocol signaling (v3+) activate one week after 5/6 of the voting power has signaled for a particular version
- Upgrades using in-protocol signaling (v3+) activate two weeks after 5/6 of the voting power has signaled for a particular version

### Upcoming upgrade

Expand All @@ -38,7 +38,7 @@ Key features include:
- [CIP-27](https://cips.celestia.org/cip-27.html): Block limits for number of PFBs and non-PFBs
- [CIP-28](https://cips.celestia.org/cip-28.html): Transaction size limit

Unlike the Lemongrass upgrade, there will not be a pre-programmed upgrade height. Instead, validators will signal their readiness for v3 through in-protocol signaling, and the upgrade will automatically activate one week after 5/6 of voting power have signaled for a particular version.
Unlike the Lemongrass upgrade, there will not be a pre-programmed upgrade height. Instead, validators will signal their readiness for v3 through in-protocol signaling, and the upgrade will automatically activate two weeks after 5/6 of voting power have signaled for a particular version.

:::info
Validators should ensure they are running a v3 binary before signaling support for the upgrade.
Expand Down
Loading