You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
SectorOnChainInfo
needs aProofExpiration
epoch. It should be set as follows:ExpirationSet
needs a new fieldFaultySectors
which will contain the bitfield of sectors expiring "early" due to being faulty for too long (previous this was inEarlySectors
).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.The text was updated successfully, but these errors were encountered: