Sector expiration issue #10957
Answered
by
beck-8
yushui468
asked this question in
Storage Provider
Sector expiration issue
#10957
-
|
Is the sector expiration and invalid computing power calculated based on the "expiration" field, or is it a proof of time and space on the day of installation? |
Beta Was this translation helpful? Give feedback.
Answered by
beck-8
Jun 21, 2023
Replies: 1 comment
-
|
expiration = expiration + deadline id * 60 For example $ ./lotus state sector f02224517 6938
SectorNumber: 6938
SealProof: 9
SealedCID: bagboea4b5abcbhzjnbplkqr3mwven6t5nypf3unoqthgem5zfqc7b4tysica5hqf
DealIDs: [42336981]
Activation: 2967225 (21 Jun 23 12:52 CST, 1 minute ago)
Expiration: 4512159 (08 Dec 24 23:19 CST, in 1 year 24 weeks)
DealWeight: 0
VerifiedDealWeight: 106167056071655424
InitialPledge: 4.062703782942331735 FIL
ExpectedDayReward: 0.005615390004238015 FIL
ExpectedStoragePledge: 0.108739997562387975 FIL
Deadline: 3
Partition: 0reality Expiration = Expiration + 3 * 60 |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
TippyFlitsUK
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
expiration = expiration + deadline id * 60
For example
$ ./lotus state sector f02224517 6938 SectorNumber: 6938 SealProof: 9 SealedCID: bagboea4b5abcbhzjnbplkqr3mwven6t5nypf3unoqthgem5zfqc7b4tysica5hqf DealIDs: [42336981] Activation: 2967225 (21 Jun 23 12:52 CST, 1 minute ago) Expiration: 4512159 (08 Dec 24 23:19 CST, in 1 year 24 weeks) DealWeight: 0 VerifiedDealWeight: 106167056071655424 InitialPledge: 4.062703782942331735 FIL ExpectedDayReward: 0.005615390004238015 FIL ExpectedStoragePledge: 0.108739997562387975 FIL Deadline: 3 Partition: 0reality Expiration = Expiration + 3 * 60