Espresso Systems primary sources — 2026-04-25

Status

• No single classic whitepaper or litepaper found during this pass.
• Primary source of truth appears to be the official site, network docs, and public GitHub organization.

Reviewed primary sources

• Official site: https://www.espressosys.com/
• Docs home / network landing page: https://docs.espressosys.com/
• Docs index: https://docs.espressosys.com/network/llms.txt
• System overview: https://docs.espressosys.com/network/concepts/the-espresso-network/system-overview.md
• How Espresso fits into your architecture: https://docs.espressosys.com/network/concepts/espresso-in-the-modular-stack.md
• Rollup architecture: https://docs.espressosys.com/network/concepts/rollup-architecture.md
• Rollup developer guide: https://docs.espressosys.com/network/guides/rollup-developers.md
• GitHub org: https://github.com/EspressoSystems

Notes

• The official positioning is broader than “shared sequencer”: Espresso is pitched as custom-chain infrastructure that can provide confirmations, sequencing, data availability, and cross-chain application support.
• The docs explicitly frame Espresso as a base layer for rollups and describe how rollups, Espresso, and an L1 interact for ordering, checkpointing, and settlement.
• Architecture docs emphasize fast confirmations backed by BFT consensus and compatibility with multiple data-availability choices rather than forcing a single stack decision.
• The operator/developer docs explicitly mention stablecoins, tokenized assets, exchanges, and payment systems as target application classes, making Espresso relevant to crypto-financial infrastructure rather than only rollup middleware.
• The GitHub organization exposes active protocol, integration, contract, and cryptography repositories, which reinforces that code+docs are the real first-party technical source surface.