Difference between revisions of "Byzantine fault"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
[[wikipedia:Byzantine fault]] | [[wikipedia:Byzantine fault]] | ||
| − | + | ||
* Practical Byzantine Fault Tolerance ([[PBFT]]) | * Practical Byzantine Fault Tolerance ([[PBFT]]) | ||
* [[decentralized Byzantine fault tolerant (dBFT)]] | * [[decentralized Byzantine fault tolerant (dBFT)]] | ||
| + | * [[Algorand]] | ||
| + | * [[Tendermint]] | ||
== Related == | == Related == | ||
Revision as of 21:33, 15 August 2022
- Practical Byzantine Fault Tolerance (PBFT)
- decentralized Byzantine fault tolerant (dBFT)
- Algorand
- Tendermint
Related
- Consensus
- Byzantine fault tolerance (BFT)
See also
- Byzantine fault tolerance (BFT), Byzantine fault, Tendermint
- 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
Advertising:
