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

FIP-0047: Migration #123

Open
geoff-vball opened this issue Nov 25, 2022 · 2 comments
Open

FIP-0047: Migration #123

geoff-vball opened this issue Nov 25, 2022 · 2 comments
Assignees
Labels

Comments

@geoff-vball
Copy link
Contributor

  • Each SectorOnChainInfo needs a ProofExpiration epoch. It should be set as follows:

During migration at network upgrade, each sector’s ProofExpiration is set to that value it would have if it had initially been set to SectorActiviation + MaxProofDuration and then refreshed until the proof expiration is no less than the commitment expiration.

  • Each Partition's ExpirationSet needs a new field FaultySectors which will contain the bitfield of sectors expiring "early" due to being faulty for too long (previous this was in EarlySectors). EarlySectors will now contain the bitfield of sectors expiring "early" due to proof expiration. This should be set to an empty bitfield for the migration.
@jennijuju
Copy link
Member

@Kubuxu could you please review and confirm all migration is captured?

@jennijuju jennijuju added the P1 label Nov 25, 2022
@Kubuxu
Copy link

Kubuxu commented Nov 25, 2022

Sounds right

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

Successfully merging a pull request may close this issue.

3 participants