Skip to content
This repository has been archived by the owner on Jun 6, 2023. It is now read-only.

Sector Expiration Fix #877

Closed
ZenGround0 opened this issue Aug 3, 2020 · 3 comments
Closed

Sector Expiration Fix #877

ZenGround0 opened this issue Aug 3, 2020 · 3 comments
Labels
cleanup Technical debt recovery and other cleanup work discussion P2 Medium priority, beneficial for network functionality and growth

Comments

@ZenGround0
Copy link
Contributor

#836 rushed through a sector expiration change that doesn't seem exactly right. I think I should have changed max sector lifetime and instead changed max extension

  1. SectorMaximumLifetime() should be changed to 540 days from five years
  2. MaxSectorExpirationExtension should move back to 366.

@zixuanzh @nicola let me know if this sounds alright with you. This doesn't matter for incentinet since it's not going to last 180 days.

@anorth FYI

@anorth
Copy link
Member

anorth commented Aug 4, 2020

I don't think any change is needed. We should not imply the arithmetic around subtracting 180 from 540. We should set this value based on any independent restriction that exists.

@zixuanzh's comments explicitly say there is no restriction. We could set this to max uint64 to be clear about that. Otherwise set it to equal max sector lifetime ?

@zixuanzh
Copy link
Collaborator

zixuanzh commented Aug 5, 2020

@nicola raised that there might be a need for MinSectorLifetimeExtension.

It seems reasonable to set that to the MinSectorLifetime. In other words, given a MinSectorLifetime of 180 days and MaxSectorLifetime of 540 days. Sectors can be extended at minimum 180 days at a time up till the maximum SectorLifetime (540 days) since the StartEpoch of the original sector. There is no independent restriction for MaxSectorLifetimeExtension but the practical bound is 540 - 180.

@anorth anorth added blocked Implementation blocked on information or decisions external to actors team discussion labels Aug 6, 2020
@anorth
Copy link
Member

anorth commented Aug 6, 2020

I'll await the promotion of "might" to "must".

@anorth anorth added cleanup Technical debt recovery and other cleanup work P2 Medium priority, beneficial for network functionality and growth and removed blocked Implementation blocked on information or decisions external to actors team labels Aug 20, 2020
@anorth anorth closed this as completed Oct 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cleanup Technical debt recovery and other cleanup work discussion P2 Medium priority, beneficial for network functionality and growth
Projects
None yet
Development

No branches or pull requests

3 participants