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

Feat/nv19 #10592

Merged
merged 1 commit into from
Mar 29, 2023
Merged

Feat/nv19 #10592

merged 1 commit into from
Mar 29, 2023

Conversation

arajasek
Copy link
Contributor

Related Issues

nv19 is planned for May: filecoin-project/core-devs#123 (reply in thread)

Proposed Changes

Introduces the skeleton for nv19 and nv20 into Lotus without any upgrade epochs, or code / state changes / migrations. Has no effect except on devnets and tests.

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

  • Commits have a clear commit message.
  • PR title is in the form of of <PR type>: <area>: <change being made>
    • example: fix: mempool: Introduce a cache for valid signatures
    • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
    • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

@arajasek arajasek requested a review from a team as a code owner March 29, 2023 17:00
@arajasek arajasek force-pushed the feat/nv19 branch 4 times, most recently from b91b16c to 8c9737c Compare March 29, 2023 20:11
Update to go-state-types v0.11.0-alpha-1

Introduce dummy v11 actor bundles

Make new actors adapters

Add upgrade to Upgrade Schedules

make jen

Update to go-state-types v0.11.0-alpha-2
@@ -59,7 +59,11 @@ var UpgradeSkyrHeight = abi.ChainEpoch(-19)

var UpgradeSharkHeight = abi.ChainEpoch(-20)

var UpgradeHyggeHeight = abi.ChainEpoch(30)
var UpgradeHyggeHeight = abi.ChainEpoch(-21)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since I'm here, why do we go in reverse order (Hygge < Shark) again?


var UpgradeLightningHeight = 30

var UpgradeThunderHeight = 1000
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For devnet testing of nv19 might we want to keep Thunder in the far future by default?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably this only matters for butterfly and calibration and those will be set to realistic testing heights later anyway

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this is solely for folks running little 2k devnets on this branch specifically, so I'm not too fussed (calibration etc. will continue to sync well with this branch).

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

Successfully merging this pull request may close these issues.

2 participants