Summary: Hyli is a blockchain and settlement layer built around private yet verifiable financial applications, especially for European regulated actors. Its core claim is that public chains reveal too much for institutional finance while permissioned chains require too much trust, so Hyli moves application execution and state offchain, keeps only sequencing and proof verification onchain, and uses zero-knowledge proofs plus selective disclosure to let institutions settle, tokenize, and comply without exposing sensitive transaction data.
What it does:
Sequences application intents onchain as blob transactions, then settles resulting state transitions later through proof transactions rather than re-executing application logic onchain
Lets apps run offchain in Rust, Noir, SP1, RISC Zero, and other proving environments, while Hyli verifies proofs and commits compact state digests onchain
Emphasizes regulated-finance use cases such as private stablecoin issuance, confidential asset tokenization, institutional payment networks, and privacy-preserving compliance workflows
Supports native proof composition so multiple proofs and even different proving schemes can be combined in one transaction without forcing recursive verification inside the app itself
Uses pipelined proving to separate fast sequencing from slower proof generation, aiming for Web2-like confirmation speed while preserving cryptographic settlement guarantees
Uses Autobahn consensus, a parallel-lane and cut-based design, as the sequencing/finality layer underneath the proof-settlement architecture
Key claims:
The official docs repeatedly describe Hyli as a confidential yet verifiable financial settlement infrastructure for European regulated actors, designed around MiCA and AML/CTF realities rather than generic consumer-chain use cases
Hyli argues that public chains are too transparent for institutions and permissioned chains are not verifiable enough, so its main architectural move is to keep the proof public while keeping the underlying transaction data private
The docs frame Hyli not as a classic smart-contract VM chain but as a proof-powered L1 where apps execute and maintain state offchain, submit proofs asynchronously, and only settle commitments onchain
Native proof composition and pipelined proving are major categorization signals: Hyli wants to be a universal proof-and-settlement layer for multi-proof financial applications, not just a privacy feature bolted onto an L1
The current first-party source of truth is the docs corpus plus open-source repos and llms.txt; the main whitepaper-like artifact clearly surfaced in this pass is the Autobahn consensus paper, which describes a component of the stack rather than Hyli’s full product/protocol on its own
Whitepaper: No single canonical Hyli protocol whitepaper or litepaper was clearly surfaced in this pass. The most informative primary sources are the docs hub, llms.txt, the website’s “What is Hyli” page, and the main GitHub repo. A linked Autobahn whitepaper exists for the consensus subsystem, but that is best treated as a component reference rather than Hyli’s full canonical protocol whitepaper; see ../whitepapers/hyli-primary-sources-2026-04-27.md.