specs
specs copied to clipboard
filecoin-project
The Filecoin protocol specification
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 [spec](https://github.com/filecoin-project/specs/blob/master/actors.md#commitsector) shows that the [`SubmitPoSt`](https://github.com/filecoin-project/specs/blob/master/actors.md#submitpost) and [`CommitSector`](https://github.com/filecoin-project/specs/blob/master/actors.md#commitsector) methods rely on a function called `ProvingPeriodDuration` which produces the number of blocks in a proving period given a sector size. We...
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...
https://github.com/arsstone/specs/blob/master/drafts/proposal-on-filecoin-pledge-mechanism/proposal-on-filecoin-pledge-mechanism.md This proposal involves the Filecoin pledge mechanism, which aims to reduce the probability of penalties under the premise of ensuring user data storage, and to avoid the miner withdrawing...
Storage Miners must be replying before the gen. attack threshold, however, EC can have a series of null blocks, if there gen. attack threshold (we are working on finding this...
The [`submitPoSt`](https://github.com/filecoin-project/specs/blob/14a7719d218ef616e40088bccd0b405b41f8b2eb/actors.md#submitpost) message includes a parameter `faults` of type `[]FaultSet`. The [`GeneratePost`](https://github.com/filecoin-project/specs/blob/master/proofs.md#generatepost) operation can return a slice of faults. Couple of questions: 1. What is a `FaultSet`? Is it just...
#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,...
if a miner and a client make a deal, and the miner never posts the sector, the client should have some recourse. The miner can never get paid for this...
From `network-protocols.md` there is a comment in the pseudocode of the storage deal proposal validation pseudocode above a call to `ValidateSignature(prop.Signature, prop.ClientAddress)` that reads: "Note: Maybe this is unnecessary, and...
If a client makes a deal with a miner, the miner accepts, receives the data, then sends back confirmation of having received the data, the client should have some recourse...