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
cost - the cost to pledge the given sector (hypothetically) penalty - the hypothetical term penalty on the sector
For the variables we need to supply to the TerminateSector call:
height uint64 => current block height
sectorSize uint64 => get from the miner ID
qaPowerSmoothedPositionEstimate *corebig.Int => network params
qaPowerSmoothedVelocityEstimate *corebig.Int => network params
rewardSmoothedPositionEstimate *corebig.Int => network params
rewardSmoothedVelocityEstimate *corebig.Int => network params
activation uint64 => current block height
expiration uint64 => hardcode to 18 months
dealWeight *corebig.Int => hardcode to 0 for now
verifiedDealWeight *corebig.Int => percQAP passed as a parameter
expectedDayReward *corebig.Int => network parameter based on sector power
expectedStoragePledge *corebig.Int => network parameter
powerBaseEpoch uint64 => ???
replacedDayReward *corebig.Int => IGNORE FOR NOW
NOTE that this does not have to do with any existing economics pledged in sectors for any particular single miner. It's helpful to understand how 1 FIL will devalue upon pledging
The text was updated successfully, but these errors were encountered:
Schwartz10
changed the title
Research task: create lossOnPledge method
Research task: create termPenaltyOnPledge method
Jul 8, 2024
It's important to understand what new hypothetical termination penalties you will incur as a miner if you pledge new FIL.
The method interface:
cost
- the cost to pledge the given sector (hypothetically)penalty
- the hypothetical term penalty on the sectorFor the variables we need to supply to the TerminateSector call:
NOTE that this does not have to do with any existing economics pledged in sectors for any particular single miner. It's helpful to understand how 1 FIL will devalue upon pledging
The text was updated successfully, but these errors were encountered: