Pith. sign in

REVIEW 3 cited by

Narwhal and Tusk: A DAG-based Mempool and Efficient 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

arxiv 2105.11827 v4 pith:7L7PEG3J submitted 2021-05-25 cs.CR cs.DC

classification cs.CRcs.DC
keywords latencynarwhalconsensusfaultsthroughputhighnarwhal-hotstuffperformance
verification ladder T0 review T1 audit T2 compute T3 formal

Signed reviews

No signed human review yet.

0 comments
read the original abstract

We propose separating the task of reliable transaction dissemination from transaction ordering, to enable high-performance Byzantine fault-tolerant quorum-based consensus. We design and evaluate a mempool protocol, Narwhal, specializing in high-throughput reliable dissemination and storage of causal histories of transactions. Narwhal tolerates an asynchronous network and maintains high performance despite failures. Narwhal is designed to easily scale-out using multiple workers at each validator, and we demonstrate that there is no foreseeable limit to the throughput we can achieve. Composing Narwhal with a partially synchronous consensus protocol (Narwhal-HotStuff) yields significantly better throughput even in the presence of faults or intermittent loss of liveness due to asynchrony. However, loss of liveness can result in higher latency. To achieve overall good performance when faults occur we design Tusk, a zero-message overhead asynchronous consensus protocol, to work with Narwhal. We demonstrate its high performance under a variety of configurations and faults. As a summary of results, on a WAN, Narwhal-Hotstuff achieves over 130,000 tx/sec at less than 2-sec latency compared with 1,800 tx/sec at 1-sec latency for Hotstuff. Additional workers increase throughput linearly to 600,000 tx/sec without any latency increase. Tusk achieves 160,000 tx/sec with about 3 seconds latency. Under faults, both protocols maintain high throughput, but Narwhal-HotStuff suffers from increased latency.

Discussion (0). Continue with ORCID to comment.

Forward citations

Cited by 3 Pith papers

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

  1. Formal Verification of Blockchain Nonforking in DAG-Based BFT Consensus with Dynamic Stake

    cs.LO 2025-04 accept novelty 8.0 of 10 full

    A machine-checked ACL2 proof shows that a DAG-based BFT consensus protocol with dynamic stake never forks, provided faulty stake in every committee is below one third.

  2. Consensus as Collapse Policy: Communication Evidence, Horizons, and Prefix Decisions

    cs.DC 2026-07 conditional novelty 5.5 of 10

    Consensus is lawful collapse of order-2 communication evidence into order-1 outputs under legitimacy, horizon, and repair rules.

  3. Bullshark on Narwhal: Implementation-level Workflow Analysis of Round-based DAG Consensus in Theory and Practice

    cs.CR 2025-07 conditional novelty 2.0 of 10

    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.

Pith tools