entity · derived

Byzantine fault tolerance

4 claims across 2 works, 2018–2025.

Derived node: assembled mechanically from the claims carrying byzantine-fault-tolerance. 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-012 2018 failure: No consensus protocol can guard against Byzantine faults when a single transaction is worth more than the promise of all future fees for the entire platform, because in that case a party can profitabl
3125827-029 2018 mechanism: If a Byzantine producer equivocates during a network partition and wins validation pools in separate subnets, the fork is not permanent: once connectivity is restored the next honest producer points t
5225296-019 2025 condition: SPoS inherits PBFT's stability threshold: the three-phase pre-prepare, prepare, and commit protocol secures agreement despite Byzantine behavior, but formal analysis proves stability only while fewer