✳flâneur — a map of the web's best reading
davidrusu/bft-crdts: Byzantine Fault Tolerant CRDT's and other Eventually Consistent Algorithms
github.com · 703 words · saved by 1 readers
Byzantine Fault Tolerant CRDT's and other Eventually Consistent Algorithms
Byzantine Fault Tolerant Eventually Consistent Algorithms This research was funded by Maidsafe and open sourced at their request. (MIT/BSD-3) The repository contains a byzantine fault tolerant systems for achieving network agreement over eventually consistent algorithms. The system is implemented as a three layered onion. The center is the eventually consistent algorithm, e.g. CRDT's or perhaps a causal asset transfer system (AT2). This core is responsible for validating and applying incoming operations, this is the "business logic" of the system. On top of the core we layer an implementation
Explore this link on the map →related reading
- Building a BFT JSON CRDTjzhao.xyz
- A Distributed Systems Reading Listferd.ca
- Let’s take a crack at understanding distributed consensuspreethikasireddy.com
- Consensus Canon - a16z cryptoa16zcrypto.com
- practical Byzantine Fault Tolerance(pBFT) - GeeksforGeeksgeeksforgeeks.org
- Byzantine fault - Wikipediaen.wikipedia.org
- The Hitchhiker's Guide to Ethereum - Delphi Digitalmembers.delphidigital.io
- CRDTs go brrrjosephg.com
- How to do distributed locking - Martin Kleppmann's blogmartin.kleppmann.com
- Conflict-free replicated data type - Wikipediaen.wikipedia.org
- What is the difference between PBFT, Tendermint, HotStuff, and HotStuff-2?decentralizedthoughts.github.io
- Raft Consensus Algorithmraft.github.io