Metraipolis › archive › dc_ff600a97e92d
Barnacle: Adaptive Multi-Leader Scheduling for DAG-Based Consensus — arXiv:2609.03978
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.03978
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-17T01:47:28.940Z
- SHA-256 of the archived text
8c72433eb01bd25355e7f6c7c356af6c4cc63c3d6aa3f33ea42210de6ce56c7b- Stable URL of this page
https://metraipolis.com/documento/dc_ff600a97e92d
How to cite
Barnacle: Adaptive Multi-Leader Scheduling for DAG-Based Consensus — arXiv:2609.03978 — arXiv (en), https://arxiv.org/abs/2609.03978 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_ff600a97e92d (Metraipolis archive dc_ff600a97e92d, sha256 8c72433eb01bd25355e7f6c7c356af6c4cc63c3d6aa3f33ea42210de6ce56c7b)
BibTeX
@misc{dcff600a97e92d,
title = {Barnacle: Adaptive Multi-Leader Scheduling for DAG-Based Consensus — arXiv:2609.03978},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.03978},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_ff600a97e92d; sha256 8c72433eb01bd25355e7f6c7c356af6c4cc63c3d6aa3f33ea42210de6ce56c7b},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.03978. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
In DAG-based consensus, all validators propose blocks concurrently, and designated leader blocks drive transaction commit. Having multiple leader slots per round cuts queuing latency, yet production deployments run a single leader because of head-of-line blocking: a slow leader stalls the pipeline for at least one leader timeout, and for several waves when its slot must wait for the fallback indirect decision rule. This risk grows with the leader count. We introduce Barnacle, an add-on that adapts the leader count at run time. Every interval, it measures on the agreed committed DAG the fraction of slots decided as commit by the direct rule, and drives the leader count with additive increase, multiplicative decrease. The measurement requires no extra messages and no cryptography, and is deterministic. Barnacle is generic over DAG protocols; we instantiate it on four protocols spanning the Byzantine (3f + 1, 5f + 1), crash-only (2c + 1), and mixed (5f + 3c + 1) fault models, with proven safety and liveness. Results show Barnacle matches the best static leader count in every regime: in a healthy network its latency is 6-13% lower than a single leader's, and under degradation it matches a single leader while remaining 35-56% below a static high count. We are currently collaborating with the Sui team to integrate Barnacle into the Sui blockchain. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-04 in cs.DC). Categorie arXiv: Distributed, Parallel, and Cluster Computing (cs.DC) ; Cryptography and Security (cs.CR). Pagina del lavoro: https://arxiv.org/abs/2609.03978 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-17T01:12:01.341Z dalla pagina https://arxiv.org/catchup/cs.DC/2026-09-04?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).