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: implement nv22 #11351

Conversation

simlecode
Copy link
Contributor

Related Issues

Proposed Changes

  1. nv22 upgrade name UpgradeWatermelonFixHeight
  2. add v13 bundle and generate builtin actor
  3. replace go-state-type and generate actors
  4. add nv22 upgrade actor logic
  5. add test

todo:

  1. updata filecoin-ffi to support nv22
  2. update go-state-type
  3. confirm the upgrade height of each network

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
  • If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

@simlecode simlecode requested a review from a team as a code owner October 25, 2023 05:41
@simlecode
Copy link
Contributor Author

@simlecode
Copy link
Contributor Author

@simlecode
Copy link
Contributor Author

Most tests fail because nv22 is currently not supported

image

@jennijuju
Copy link
Member

Most tests fail because nv22 is currently not supported

image

we need a PR in ref-fvm as well https://github.com/filecoin-project/ref-fvm/pull/1726/files

@Stebalien
Copy link
Member

From slack, we'll try this a different way: rename v12 to v12-rc.1 (or something like that), introduce a special calibration-only upgrade, and not introduce any new network versions.

@simlecode simlecode closed this Oct 27, 2023
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.

3 participants