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

[Forest] NV22 state migration #3856

Closed
LesnyRumcajs opened this issue Jan 8, 2024 · 2 comments · Fixed by #3955
Closed

[Forest] NV22 state migration #3856

LesnyRumcajs opened this issue Jan 8, 2024 · 2 comments · Fixed by #3955
Assignees
Milestone

Comments

@LesnyRumcajs
Copy link
Member

LesnyRumcajs commented Jan 8, 2024

Issue summary
Implement NV22 migration. It seems it will only need code IDs and system actor changes (similar to some recent calibnet patches, but all actors, not only the Miner actor).

I was overly optimistic. There may be more changes; see @lemmih comment below.

Other information and links

@LesnyRumcajs LesnyRumcajs added this to the NV22 milestone Jan 8, 2024
@LesnyRumcajs LesnyRumcajs changed the title NV22 state migration [Forest] NV22 state migration Jan 8, 2024
@lemmih
Copy link
Contributor

lemmih commented Jan 16, 2024

To do:

  1. List each accepted FIP.
  2. For each FIP, describe the changes (if any) to the actor states and how to migrate the structures.
  3. Estimate whether pre-migration is required for acceptable performance (ie. if migration would otherwise take more than 5-10 minutes).

@LesnyRumcajs LesnyRumcajs self-assigned this Jan 22, 2024
@LesnyRumcajs
Copy link
Member Author

Accepted FIPs for NV22:

For completeness, new built-in actor codes will also need to be deployed, as usual.

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 a pull request may close this issue.

2 participants