entity · derived

Finality

4 claims across 1 works, 2018–2018.

Derived node: assembled mechanically from the claims carrying finality. A roster, not an adjudicated definition.

Every claim under this term

3125827-008 2018 condition: Given that Byzantine faults are inevitable in a distributed system, the known impossibility results force any consensus protocol to hedge: it can promise only a probability of finality and security, a
3125827-026 2018 failure: Forcing validation pools to close in finite time, which practical demand for swift resolution requires, opens the possibility of network partition and of a lack of genuine consensus, and therefore of
3125827-030 2018 failure: A 67% active validator requirement would improve finality but is excluded from the initial SPoS implementation because, by the CAP theorem, it limits the availability of the system and arbitrarily pun
3125827-034 2018 mechanism: Finality in SPoS is measurable because forking away from a given block would cost the community all sem tokens created on the chain after it, and that quantity equals half of all fees sent since the b