Skip to content
NewA calmer, faster ZeroHour

Hydrozoan: Latency-Adaptive DAG Consensus under Mixed Byzantine and Crash Faults

arXiv cs.CRby Qianyu Yu ()1 min read6 · 6 reads
AI summary · grok-4.7Summaries by Vani AI

Hydrozoan is a DAG consensus protocol that commits in two or three delays under mixed Byzantine and crash faults.

Hydrozoan is a DAG-based consensus protocol for n = 3f+c+2p+1 validators that tolerates f Byzantine and c crash faults. Leaders commit in two message delays when at most p validators are faulty and in three delays otherwise, using one DAG, no extra messages, and no view changes. Optimal-Hydrozoan tolerates one additional fast-path fault and matches a known lower bound; both protocols' safety and liveness are machine-checked in Lean 4. A geo-distributed evaluation matches Mysticeti's throughput and commits about 25% faster when the fast quorum sits in low-latency regions.

Key facts
  • Fast path commits in two message delays when at most p validators are faulty.
  • Otherwise it commits in three delays on the same DAG, with no extra messages.
  • The validator count is n = 3f+c+2p+1 under hybrid Byzantine and crash faults.
  • Safety and liveness of both variants are machine-checked in Lean 4.
  • Evaluation matches Mysticeti throughput and is about 25% faster in favorable regions.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

1 min read at arxiv.org

DAG-based consensus protocols can achieve great throughput and the optimal three-message-delay limit for n = 3f+1 consensus. While two-delay protocols exist, they pay with reduced resilience (requiring 5f+1-style committees) or rely on fallbacks that sacrifice the DAG's high throughput.

arXiv cs.CR

By Qianyu Yu · arxiv.org

Read the full article at arXiv cs.CR

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.