TaifoonTAIFOON
[ Co-branded announcement · Espresso × Taifoon ]

Espresso Systems×Taifoon.

HotShot sequencer × Taifoon V5 — shared sequencing, provable. Live integration since day one — the banner below regenerates from /api/intel/espresso every fifteen seconds so both sides can verify the wire is current.

TAIFOON×ESPRESSO NETWORK ↗INTEGRATION LAGGING

HotShot finality, anchored against the SuperRoot.

Taifoon indexes Espresso's mainnet sequencer block-by-block and threads HotShot consensus through V5 as a first-class finality type — alongside Ethereum PoS, Arbitrum BOLD, BSC fast finality, and seven others. Espresso-sequenced rollups inherit the same six-layer proof envelope, with the HotShotLightClient on Ethereum L1 as the BN254 Plonk anchor.

Espresso tip
19,206,310
Our height
19,114,232
Blocks indexed
4,938,633
Polling
0s ago
HotShotLightClient · Ethereum mainnet
0x95Ca91Cea73239b15E5D2e5A74d02d6b5E0ae458
[ co-branded graphic · 1200 × 630 ]

The shareable card.

Espresso Systems × Taifoon partnership — HotShot sequencer × Taifoon V5 — shared sequencing, provable

↗ open the raw graphic — right-click → save for sharing

[ X posts · paste-ready, both voices ]

One post each side.

[ Taifoon voice ]
post from @taifoonOS
248 / 280
[ Partner voice ]
copy for @EspressoSys to post
251 / 280
[ thesis · why we lead with proofs, not pre-confirmations ]

Pre-confirmation is the floor; a six-layer proof is the ceiling.

Espresso ships pre-confirmations in seconds because HotShot consensus finalizes the block before Ethereum L1 even sees it. That solves the hard part — getting validators to agree on transaction order. But cross-chain consumers still have to ask: can I prove this block landed without re-running a full HotShot node?

Taifoon answers that. We index every Espresso block the moment it lands, derive a V5 cryptographic proof that binds the block hash to the HotShotLightClient state on Ethereum, and serve the proof through the same envelope solvers already use for Arbitrum BOLD, BSC fast finality, and seven other consensus families. Same wire, one more row in the finality registry.

The integration is structural — not a press release waiting for code. The links below are the ones we'd hand to any third party who wants to verify the claim end-to-end.

[ anchors · every reference verifiable ]

What you can hit yourself.

[ live numbers · last probe ]
No live probe attached.
/claim/espresso · co-branded pressNumbers regenerate per request from declared sources