Alex North
Alex North
The TokenAmount type is currently just an alias for BigInt. This means values can usually be transparently interpreted, compared etc between TokenAmount and other types, despite TokenAmount having a logical...
I think I saw a comment somewhere from @Stebalien that the ResolveAddress syscall should be removed, and instead be an explicit method send to the InitActor. It's been omitted in...
From @raulk: Right now it's possible for account actors to perform naked sends (method num = 0) to singleton actors (e.g. system, market, power, etc.), from which the funds will...
The spec currently contains some complicated data structures for representing layers of faults and "recovered" sectors. Explanation is lacking, but I think that all exists to represent the case that...
Can a sector previously committed and proven, and subsequently either declared "done" or as a fault, be re-committed without re-sealing? Is there any need for the challenge embedded in the...
`SubmitPost` was recently changed to include: ``` if chain.Now() > miner.ProvingPeriodEnd+GenerationAttackTime(miner.SectorSize) { // slashing ourselves SlashStorageFault(self) return } ``` Slashing oneself doesn't seem to make much sense: - We expect...
The actor spec contains placeholders for the late fee and temporary sector failure fee. The late fee needs to become a function of the miner's sector size, which determines its...
The [faults spec](https://github.com/filecoin-project/specs/blob/master/faults.md) for a consensus fault states that > All of the miner's pledge collateral and all of their power is irrevocably slashed For an unreported storage fault, it...
#60 was closed without actually defining storage collateral anywhere. - What is the function for storage collateral requirements? Is storage collateral a fixed amount per byte? Or, like pledge collateral,...
This is a tracking issue for a proposal that has been made over in FIPs: https://github.com/filecoin-project/FIPs/discussions/379