-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: Set upgrade heights and change codename #11599
Conversation
6179fe4
to
b95715b
Compare
a669b5d
to
7181cd3
Compare
3e6db1c
to
be342eb
Compare
Update upgrade heights Co-Authored-By: Steven Allen <steven@stebalien.com>
a203c73
to
3426289
Compare
build/params_2k.go
Outdated
|
||
var UpgradeMangoHeight = UpgradePineappleHeight + 10 | ||
var UpgradeMangoHeight = UpgradeDragonHeight + 10 |
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.
Per discussion, we'll probably wind up going with something like + 100
instead. But that doesn't have to change in this PR.
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.
Updated to +100 in 9112e85.
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.
Do we also want the Drand switch to be +100
epochs away from the nv22 upgrade in the butterfly/calibration/mainnet ?
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.
Do we also want the Drand switch to be +100 epochs away from the nv22 upgrade in the butterfly/calibration/mainnet ?
We really only care about mainnet.
@arajasek can we make this 120 so it falls on an hour mark?
Update epoch after nv22 DRAND switch
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.
Quibbles over names but this looks correct.
@@ -89,10 +89,10 @@ const UpgradeWatermelonFixHeight = 1070494 | |||
// 2023-11-21T13:00:00Z | |||
const UpgradeWatermelonFix2Height = 1108174 | |||
|
|||
// ?????? | |||
const UpgradePineappleHeight = 999999999999999 | |||
// 2024-02-27T14:00:00Z |
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.
Verified.
Make the codename for the Drand-change inline with Dragon style.
Proposed Changes
1390534
which is2024-02-27T14:00:00Z
UpgradePhoenixHeight
to 120 epochs after the nv22 upgrade.5760
which is two days from reset, allowing for us to get some states in the network before the upgrade height.Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, testarea
, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps