REVIEW 12 cited by
The latest gossip on BFT consensus
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
The paper presents Tendermint, a new protocol for ordering events in a distributed network under adversarial conditions. More commonly known as Byzantine Fault Tolerant (BFT) consensus or atomic broadcast, the problem has attracted significant attention in recent years due to the widespread success of blockchain-based digital currencies, such as Bitcoin and Ethereum, which successfully solved the problem in a public setting without a central authority. Tendermint 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.
Forward citations
Cited by 12 Pith papers
-
From Permissioned to Proof-of-Stake Consensus
A generic compiler transforms any permissioned consensus protocol into a proof-of-stake permissionless protocol with the same fault tolerance, plus accountability.
-
Multimmit: Extending Blocks for Faster Finality
Multimmit finalises transaction blocks in one voting round with roughly 3δ average latency from dissemination, confining a faulty producer's damage to its own chain.
-
The Carnot Bound: Limits and Possibilities for Bandwidth-Efficient Consensus
Two-round-finality leader-based consensus cannot beat ~2.5 data expansion; three-round Carnot protocols reach near-1 under favorable conditions and 1.33–1.5 under attack.
-
Symmetry all the way down
Asymmetric Byzantine quorum systems add no extra solvability for depth-two-or-higher tasks; a depth-2 compiler produces an equivalent symmetric system, and no depth-1 compiler exists.
-
Duet: Co-Optimizing P2P Message Propagation and Rotating-Leader Consensus
Recorded network geography lets Duet rotate proposers in latency order and broadcast blocks over latency-aware trees with a gossip fallback driven by consensus votes, yielding up to 7.26× peak throughput over gossip o...
-
Censorship Resistance and Throughput with Multiple Concurrent Proposers
Under a bribery model, multiple concurrent proposers raise the cost of censoring a transaction roughly linearly with the number of proposers, and a fee rule that penalizes duplicated inclusion dominates on both censor...
-
BlueBottle: Fast and Robust Blockchains through Subsystem Specialization
A two-layer consensus architecture uses a faster n=5f+1 DAG core plus a synchronous guard layer to reach sub-second finality with accountable recovery.
-
Recipe: Hardware-Accelerated Replication Protocols
Recipe transforms crash-fault-tolerant protocols into Byzantine-fault-tolerant ones using TEEs, with 2f+1 replicas and measured speedups up to 24x over PBFT.
-
TNIC: A Trusted NIC Architecture
TNIC is a SmartNIC-based trusted NIC architecture that implements non-equivocation and transferable authentication in hardware, so crash-fault-tolerant protocols can be transformed for Byzantine settings with 2f+1 replicas.
-
Fast and Interactive Byzantine Fault-tolerant Web Services via Session-Based Consensus Decoupling
A two-layer BFT web service that buffers session operations for instant feedback and commits them later to full consensus is demonstrated in a supply chain prototype; the claimed security guarantee for the fast layer ...
-
BLOCKS: Blockchain-supported Cross-Silo Knowledge Sharing for Efficient LLM Services
BLOCKS combines a Cosmos-based blockchain, a reputation mechanism, and a priority cache to let LLMs retrieve prompts from untrusted knowledge silos.
-
Bullshark on Narwhal: Implementation-level Workflow Analysis of Round-based DAG Consensus in Theory and Practice
A descriptive, implementation-level workflow analysis of the existing Bullshark-on-Narwhal consensus protocol, based on the Sui codebase, with no new experiments or derivations.
Discussion (0). Continue with ORCID to comment.