-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ec clarifications and updates #334
Changes from all commits
7604111
68b61f8
3e0272f
94879f8
d68b9c7
ae73147
72f22c0
cf2cb74
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -65,6 +65,10 @@ See [Filecoin Proofs](proofs.md) | |
|
||
*** *A deal in a Filecoin market is made when a bid and ask are matched, corresponding to an agreement on a service and price between a miner and client. | ||
|
||
#### Election Proof | ||
|
||
An `ElectionProof` is derived from a past `ticket` and is included in every block header. The `ElectionProof` proves that the miner was eligible to mine a block in that `round`. | ||
|
||
#### Erasure coding | ||
|
||
Erasure coding is a strategy through which messages can be lengthened so as to be made recoverable in spite of errors. | ||
|
@@ -73,7 +77,7 @@ See [Wikipedia](https://en.wikipedia.org/wiki/Erasure_code) | |
|
||
#### Epoch | ||
|
||
An epoch refers to the period over which a given random seed is used in Expected Consensus. In the current Filecoin implementation, each round is an epoch. | ||
An `epoch` is the period in which a new block is generated. There may be multiple `rounds` in an epoch. | ||
|
||
#### Fault | ||
|
||
|
@@ -101,6 +105,12 @@ The Generation Attack Threshold is equal to the Polling Time + some Grace Period | |
|
||
#### GHOST | ||
|
||
[GHOST](https://eprint.iacr.org/2013/881.pdf) is an acronym for `Greedy Heaviest Observable SubTree`, a class of blockchain structures in which multiple blocks can validly be included in the chain at any given height or round. GHOSTy protocols produce blockDAGs rather than blockchains and use a weighting function for fork selection, rather than simply picking the longest chain. | ||
|
||
#### Height | ||
|
||
`Height` refers to the number of `TipSets` that have passed between this `TipSet` and the genesis block (which starts at block height 0). If a `TipSet` contains multiple blocks, each block in the TipSet will have the same `height`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please say how this interacts with null blocks here There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. FWIW the go-filecoin code, and everyones intuitions, say that "height" is the number of rounds, not the number of tipsets. We'll be swimming upstream to redefine that here. At present, the code doesn't have a use for a count of the non-null tips. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. to be handled in a different PR per #351 |
||
|
||
#### Leader | ||
|
||
A leader, in the context of Filecoin consensus, is a node that is chosen to propose the next block in the blockchain. | ||
|
@@ -151,7 +161,11 @@ A piece is a portion of a file that gets fitted into a sector. | |
|
||
Security Parameter. Polling time is the time between two online PoReps in a PoSt proof. | ||
|
||
#### Power table | ||
#### Power Fraction | ||
|
||
A miner's `Power Fraction` is the ratio of their committed storage over Filecoin's committed storage. It is used in leader election. | ||
|
||
#### Power table | ||
|
||
The power table is an abstraction provided by the Filecoin storage market that lists the `power` of every miner in the system. | ||
|
||
|
@@ -203,7 +217,9 @@ Repair refers to the processes and protocols by which the Filecoin network ensur | |
|
||
#### Round | ||
|
||
A round refers to the period over which a new leader election occurs and a block is generated if a leader is found. Typically this means a new block will be mined at every round, though some rounds may see 0 or multiple blocks generated. | ||
A round refers to the period over which a new leader election occurs and a block is generated if a leader is found. Typically this means a new block will be mined at every round, though. | ||
|
||
A `round` is the period in which a miner runs leader election to attempt to generate a new block. It may succeed, or zero or multiple blocks may be generated instead in that round. Every `round`, one `ticket` is produced. Thus, the duration of a round is currently bounded by the duration of the Verifiable Delay Function (VDF) that is run to generate a `ticket`. Because one `ticket` is produced per `round`, the number of `tickets` is the same as the number of `rounds` that have passed. | ||
|
||
#### SEAL/UNSEAL | ||
|
||
|
@@ -233,21 +249,24 @@ In the context of: | |
|
||
#### Ticket | ||
|
||
Some unpredictable element generated by the system for two uses: | ||
|
||
- as a random challenge to PoSTs. | ||
- to elect a leader in Expected Consensus. | ||
|
||
See more on [Expected Consensus](expected-consensus.md) and [PoSTs](proofs.md). | ||
A `ticket` is used as a source of randomness in EC leader election. Every block depends on an `ElectionProof` derived from a `ticket`. At least one new `ticket` is produced with every new block. Ticket creation is described [here](./expected-consensus.md#Ticket-generation). | ||
|
||
#### TipSet | ||
|
||
A collection of blocks mined by different miners, each an elected leader of a given epoch. All tip sets have the same parent-set and epoch number (height). TODO add picture. | ||
A `TipSet` is a set of blocks that have the same parent set and same number of `tickets`, which implies they will have been mined at the same `height`. A `TipSet` can contain multiple blocks if more than one miner successfully mines a block in the same `round` as another miner. | ||
|
||
#### Verifiable | ||
|
||
Something that is verifiable can be checked for correctness by a third party. | ||
|
||
#### VDF | ||
|
||
A verifiable function that guarantees a time delay given some hardware assumptions and a small set of requirements. These requirements are efficient proof verification, random output, and strong sequentiality. Verifiable delay functions are formally defined by [\[BBBF]](https://eprint.iacr.org/2018/601). | ||
|
||
```text | ||
{proof, value} <—- VDF(public parameters, seed) | ||
``` | ||
|
||
#### VM | ||
|
||
Virtual Machine. The Filecoin VM refers to the system by which changes are applied to the Filecoin system's state. The VM takes messages as input, and outputs state. | ||
|
@@ -256,6 +275,18 @@ Virtual Machine. The Filecoin VM refers to the system by which changes are appli | |
|
||
Held by an actor as part of a payment channel to complete settlement when the counterparty defaults. | ||
|
||
#### VRF | ||
|
||
A verifiable random function that receives {Secret Key (SK), seed} and outputs {proof of correctness, output value}. VRFs must yield a proof of correctness and a unique & efficiently verifiable output. | ||
|
||
```text | ||
{proof, value} <-- VRF(SK, seed) | ||
``` | ||
|
||
#### Weight | ||
|
||
Every mined block has a computed `weight`. Together, the `weights` of all the blocks in a branch of the chain determines the cumulative `weight` of that branch. Filecoin's Expected Consensus is a GHOSTy or heaviest-chain protocol, where chain selection is done on the basis of an explicit weighting function. Filecoin’s `weight` function currently seeks to incentivize collaboration amongst miners as well as the addition of storage to the network. The specific weighting function is defined in [Chain Weighting](expected-consensus.md#chain-weighting). | ||
|
||
#### zkSNARK | ||
|
||
Zero Knowledge Succinct ARguments of Knowledge. A way of producing a small 'proof' that convinces a 'verifier' that some computation was done correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please update this to the new IPLD schema syntax
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Holding off on specifying methods and the like for now, if that is what is meant...