• Corpus ID: 211003783

Tenderbake - Classical BFT Style Consensus for Public Blockchains

@article{Astefanoaei2020TenderbakeC,
  title={Tenderbake - Classical BFT Style Consensus for Public Blockchains},
  author={Lacramioara Astefanoaei and Pierre Chambart and Antonella del Pozzo and Edward Tate and Sara Tucci Piergiovanni and Eugen Zalinescu},
  journal={ArXiv},
  year={2020},
  volume={abs/2001.11965}
}
Our work has been originally motivated by Tezos, a public blockchain which focuses on software correctness and which enables formal reasoning and verification. To further strengthen the resilience of Tezos, which now depends on a consensus protocol delivering only probabilistic finality, we propose a consensus protocol that brings deterministic finality. Our solution is backward compatible with the current liquid proof-of-stake system underlying Tezos. The main contributions of this paper are… 
1 Citations

Figures from this paper

References

SHOWING 1-10 OF 28 REFERENCES
Blockchain Consensus Protocols in the Wild
TLDR
The process of assessing and gaining confidence in the resilience of a consensus protocols exposed to faults and adversarial nodes is discussed, and the consensus protocols in some prominent permissioned blockchain platforms with respect to their fault models and resilience against attacks are reviewed.
Consensus in the Age of Blockchains
TLDR
A systematic and comprehensive study of blockchain consensus protocols is conducted, developing a framework to evaluate their performance, security and design properties, and using it to systematize key themes in the protocol categories described above.
SoK: Consensus in the Age of Blockchains
TLDR
This survey highlights the various building blocks of blockchain consensus design, along with a discussion on their security and performance properties, and identifies research gaps and insights for the community to consider in future research endeavours.
(Leader/Randomization/Signature)-free Byzantine Consensus for Consortium Blockchains
TLDR
This paper revisits the consensus validity property by requiring that the decided value satisfies a predefined predicate, which does not systematically exclude a value proposed only by Byzantine processes, thereby generalizing the validity properties found in the literature.
Hyperledger fabric: a distributed operating system for permissioned blockchains
TLDR
This paper describes Fabric, its architecture, the rationale behind various design decisions, its most prominent implementation aspects, as well as its distributed application programming model, and shows that Fabric achieves end-to-end throughput of more than 3500 transactions per second in certain popular deployment configurations.
State Machine Replication in the Libra Blockchain
TLDR
The Libra Byzantine Fault Tolerance algorithmic core incorporates a novel round synchronization mechanism that provides bounded commit latency under synchrony and introduces a nil-block vote that allows proposals to commit despite having faulty leaders.
DFINITY Technology Overview Series, Consensus System
TLDR
DFINITY consensus algorithm is made to scale through continuous quorum selections driven by the random beacon, which gracefully handles temporary losses of network synchrony including network splits, while it is provably secure under synchrony.
The latest gossip on BFT consensus
TLDR
Tendermint is presented, a new protocol for ordering events in a distributed network under adversarial conditions that modernizes classic academic work on the subject and simplifies the design of the BFT algorithm by relying on a peer-to-peer gossip protocol among nodes.
Dissecting Tendermint
TLDR
The methodology consists in identifying the algorithmic principles of Tendermint necessary for a specific combination of communication model-adversary and proving its correctness under the most adversarial conditions: an eventually synchronous communication model and asymmetric Byzantine faults.
Correctness Analysis of IBFT
TLDR
It is shown that the IBFT protocol does not guarantee Byzantine-fault-tolerant consistency and liveness when operating in an eventually synchronous network, and modifications to the protocol are proposed to ensure both Byzantine-liveness and consistency inEventually synchronous settings.
...
...