specs
specs copied to clipboard
The Filecoin protocol specification
When a message fails to execute, do we use up all the remaining gas that was allocated for this invocation or just use the gas that was spent so far...
We shouldn't try to enforce this / make it verifiable (though we could do some things under certain tradeoffs) but we should make the spec for mining messages into blocks...
Since we use the worker key to sign blocks, any change in this address represents an entirely different probability set for block production. I believe snow white mentions this attack....
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...
As referenced in issue #60