Difference between revisions of "Byzantine fault"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
* [[Consensus]] | * [[Consensus]] | ||
* [[Tendermint]] | * [[Tendermint]] | ||
| − | * Byzantine fault tolerance (BFT) | + | * Byzantine fault tolerance (BFT) |
== See also == | == See also == | ||
Revision as of 21:32, 15 August 2022
- Algorand
- Practical Byzantine Fault Tolerance (PBFT)
- decentralized Byzantine fault tolerant (dBFT)
Related
- Consensus
- Tendermint
- Byzantine fault tolerance (BFT)
See also
- Crypto, Cryptocurrency, Blockchain, Stablecoin, Cryptocurrency address, Cryptocurrency wallet, Cryptocurrency exchange, DeFi, ZK, Crypto companies, Litecoin, Thodex, Ripple, Chainlink, BAT, Qredo (Qredo protocol), AMM, MEV, Uniswap, PoW, PoS, Proof of authority, Polkadot, Zilliqa, CryptoCurrency Security Standard (CCSS), BlockFi, Riot, Xcoex, Web3, Gas, Transfer of Funds Regulation (TFR), NodeReal, Wert, Stellar, DeSo, UTXO, dApp, Token, Boson Protocol, DeversiFi, Paxos Trust Company, Consensus, BlockchainFonds, Block (Crypto), TVL, TTD, Execution Layer (EL), Digital asset, Hashrate, MiCA, Rosetta API, Sybil attack, MELD, Crypto timeline, Cryptocurrency nodes, Ports in crypto, TRUST, VASPs, Velmie, Railgun, Quantstamp, Nakamoto Consensus, DLT
Advertising:
