Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryConsensus2022Design paperCorpus record

Jolteon and Ditto: Network-Adaptive Efficient Consensus with Asynchronous Fallback

Jolteon and Ditto. Rati Gelashvili, Lefteris Kokoris-Kogias, Alberto Sonnino, Alexander Spiegelman and Zhuolun Xiang.

Jolteon takes two rounds in the happy path. Ditto keeps that path and falls back to an asynchronous protocol when the network or the leader misbehaves.

A reading of the public document. Not a copy of it, and not a claim about a later network that reused the name.

A chain that claims responsive finality should say what it does when the leader's messages stop arriving.

The five-minute read

The defect

Chained HotStuff is fast in a good network and stalls badly when the leader is slow. Pure asynchronous protocols are robust and expensive all the time.

The rule

Jolteon takes two rounds in the happy path. Ditto keeps that path and falls back to an asynchronous protocol when the network or the leader misbehaves.

How it is put together

A quorum certificate still drives the happy path. The fallback does not wait for a timeout forever. Pace is a network property, not a moral one.

Where the claim stops

This is a permissioned BFT result.

One action, walked through

  1. A leader proposes and collects a certificate.
  2. A second round commits on the happy path.
  3. If certificates stop, the asynchronous path makes progress without that leader.
  4. How many rounds commit on the happy path?

The argument, unpacked

Why it is still on the desk

A chain that claims responsive finality should say what it does when the leader's messages stop arriving.

After the text

Aptos and later production BFTs cite this line of work. The deployment's timeouts are not the paper.

What has to be true

  • This is a permissioned BFT result.
  • The paper is not a public proof-of-stake chain.
  • Fallback has its own message cost. It is not free.

What happened after the paper

Aptos and later production BFTs cite this line of work. The deployment's timeouts are not the paper.

What to check before you use the idea

  • How many rounds commit on the happy path?
  • What triggers the fallback?
  • Does a committed certificate survive the switch?

Terms

Quorum certificate
A set of votes that proves a quorum signed one proposal.
Asynchronous fallback
A path that terminates without a timely leader.

The problem the paper names

Chained HotStuff is fast in a good network and stalls badly when the leader is slow. Pure asynchronous protocols are robust and expensive all the time.

What the design proposes

  • A quorum certificate still drives the happy path.
  • The fallback does not wait for a timeout forever.
  • Pace is a network property, not a moral one.

How the mechanism is specified

  • A leader proposes and collects a certificate.
  • A second round commits on the happy path.
  • If certificates stop, the asynchronous path makes progress without that leader.

What this page does not treat as proven

  • This is a permissioned BFT result.
  • The paper is not a public proof-of-stake chain.
  • Fallback has its own message cost. It is not free.

Why a venture studio still reads it

A chain that claims responsive finality should say what it does when the leader's messages stop arriving.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.