Aleo: Privacy-by-Default zkSNARK Layer 1 Mainnet
Aleo is a programmable privacy Layer 1 that compiles every transaction into a zero-knowledge proof off-chain, then settles only the proof on-chain. Mainnet went live on 2024-09-19, anchored by the AleoBFT DAG consensus, snarkVM execution and the Leo programming language. Unlike Zcash, which restricts privacy to shielded UTXO transfers, Aleo extends zkSNARK-based confidentiality to general-purpose smart contracts.
Aleo serves a narrow but defensible niche: developers and users who treat on-chain privacy as a non-negotiable primitive, not an opt-in shield pool. The chain ships with private records as the default state model, client-side proof generation that keeps inputs off third-party servers, and a token program that mirrors the ergonomics of ERC-20s while remaining fully shielded. Its consensus stack pairs the Bullshark/Narwhal DAG family with a coinbase puzzle proof-of-work component that compensates the prover network for the heavy zkSNARK workload Aleo demands. Compared to Zcash's UTXO-only Halo2 shielded pool, Aleo unlocks confidential DeFi, private identity, sealed-bid mechanisms and compliance-friendly disclosures inside a single L1. The ecosystem is still early: DefiLlama tracks only Pondo Protocol's liquid staking with around 22,375 USD TVL as of 2026-06-06, reflecting a sub-two-year-old mainnet rather than chain-level limitations. For non-custodial cross-chain swap routing, Aleo is the destination chain you choose when settlement privacy itself is the product, accepting that liquidity depth and bridge maturity will lag dominant L1s for years. The supported wallet stack (Leo Wallet, Puzzle Wallet, Avail Wallet), the official RPC at api.explorer.aleo.org/v1, and the developer docs at developer.aleo.org form a complete but compact onboarding surface aimed at builders rather than retail speculators.
About Aleo
Aleo was conceived as the first general-purpose programmable blockchain where privacy is the default state, not a feature bolted onto a public ledger. The project emerged from research at Cornell and the Initiative for Cryptocurrencies and Contracts (IC3), with technical roots in the Zexe paper that introduced decentralized private computation. Mainnet launched on 2024-09-19 after several years of testnet incentivization and snarkOS / snarkVM hardening. Unlike Ethereum, where every state transition is publicly visible, every Aleo transaction is a zkSNARK proof: inputs, outputs and state mutations are encrypted as private records, while only the proof of correct execution is broadcast to the network. This inversion of the default visibility model is the single most important fact a developer or analyst should internalize about Aleo.
Consensus runs on AleoBFT, a DAG-based proof-of-stake protocol derived from the Bullshark and Narwhal research line pioneered by Mysten Labs. AleoBFT separates data dissemination from consensus ordering so validators can pipeline block production and reach Byzantine fault-tolerant finality without sequential bottlenecks. Layered on top is a coinbase puzzle, a proof-of-work component that compensates a permissionless prover network for generating zkSNARK proofs. This hybrid PoS-plus-puzzle design is unusual: it acknowledges that zkSNARK proof generation is the chain's structural bottleneck and economically incentivises a competitive market of provers to attack that bottleneck. The same DAG research line later evolved into Sui's Mysticeti, which replaced Narwhal+Bullshark in Sui during 2024 — Aleo stayed closer to the original Bullshark/Narwhal split-design.
Execution happens inside snarkVM, the zero-knowledge virtual machine that runs programs written in Leo, Aleo's purpose-built Rust-flavored language. Leo compiles to circuits, not bytecode, which means every conditional branch and loop is unrolled into arithmetic constraints suitable for zkSNARK proving. The token standard pairs native records, which are private by construction, with a public token program that mimics ERC-20 ergonomics for developers who want fungible assets without rebuilding privacy from scratch. Client-side proof generation is the load-bearing user-experience choice: sensitive inputs never leave the user's device, which is a structurally stronger privacy guarantee than any mixer or rollup-based approach that relies on relayers or sequencers seeing plaintext.
Economically, Aleo issues the native ALEO token to pay for gas, stake into AleoBFT validators and reward coinbase puzzle solvers. Because every transaction carries a zkSNARK proof, gas accounting must price proof verification as well as state writes, which means Aleo's fee model is structurally different from EVM gas: it reflects circuit complexity, not just opcode count. Addresses use a Bech32m encoding with the aleo1 prefix, mirroring the segwit-style human-readable design Bitcoin pioneered. The ecosystem on 2026-06-06 is intentionally minimal — Pondo Protocol's liquid staking is the only DefiLlama-tracked deployment at roughly 22,375 USD TVL — which is consistent with a privacy chain whose first 21 months have prioritized protocol stability over TVL races.
Aleo technical parameters
Aleo's technical anchor points are three: AleoBFT DAG consensus for ordering, snarkVM zkSNARK execution for privacy and Leo as the developer-facing language. Each component is deliberately chosen to solve a different bottleneck — throughput, confidentiality and programmer ergonomics — and together they explain why Aleo's published numbers focus on theoretical proving capacity rather than the block-time and finality figures other chains lead with.
| Consensus | AleoBFT (Bullshark/Narwhal DAG-based PoS + coinbase puzzle PoW) |
|---|---|
| VM | snarkVM (zkSNARK-based execution, Leo language) |
| Block time | — |
| Finality | — |
| TPS | — typical / 20k max |
| Gas token | ALEO |
| Launched | 2024-09-19 |
| Token standard | Native records (private) + token program |
| Address | Bech32m (aleo1-prefixed) |
Consensus mechanism
AleoBFT is a directed-acyclic-graph (DAG) consensus protocol inspired by Narwhal and Bullshark, the Mysten Labs research line that also seeded Sui's earlier consensus stack before Sui migrated to Mysticeti in 2024. In a traditional chain-of-blocks BFT (think Tendermint or HotStuff), validators must agree on one block at a time before moving on. In a DAG protocol, validators concurrently broadcast their proposals into a partially-ordered graph; consensus is then about agreeing on a total order over that graph, not about producing a single canonical block per slot. This separation of data dissemination from ordering lets AleoBFT pipeline proof verification and validator voting in parallel, which is critical because zkSNARK verification is computationally heavy. Aleo layers a coinbase puzzle proof-of-work component on top of the PoS validator set: provers compete to generate zkSNARK proofs for users' transactions and earn coinbase rewards in ALEO. The block time and instant finality figures from AleoBFT are not consistently published in the official spec, so honest reporting requires saying so rather than fabricating a number. What is published is a theoretical throughput ceiling of around 20,000 TPS, a figure cited in AleoBFT upgrade announcements and tied to DAG parallelism rather than measured mainnet load.
Performance context
Read Aleo's 20,000 TPS theoretical ceiling against peer chains the way a stress-test engineer would: it is a capacity headroom claim, not an observed throughput. Solana, the highest-TPS public L1 in current production use, settles roughly 3,000 TPS typical against a 65,000 TPS theoretical max. Sui claims 297,000 TPS max but operates around 1,500 typical. Aleo currently publishes no typical-TPS, block-time or finality figure, which is appropriate honesty for a chain less than two years past mainnet launch where real-world load is still light. The relevant performance lens for Aleo is not raw transactions per second but proofs per second per dollar of prover hardware, because every transaction is a zkSNARK proof. That metric is what the coinbase puzzle economy is designed to optimize.
Aleo ecosystem map
Aleo's ecosystem on 2026-06-06 is small and developer-focused, which is consistent with a 21-month-old privacy L1 that has prioritized protocol stability over TVL marketing. DefiLlama tracks only one deployment with measurable TVL — Pondo Protocol's liquid staking — and the supporting wallet and infrastructure layer is built by three teams native to the Aleo community.
Liquid Staking
Pondo Protocol is the only DefiLlama-tracked DeFi deployment on Aleo as of 2026-06-06, holding roughly 22,375 USD TVL. It accepts ALEO deposits, delegates them across AleoBFT validators and issues a liquid receipt token usable inside Aleo's privacy-native programs.
Wallet
Leo Wallet is the flagship browser extension built by the team behind Demox Labs, with deep integration to Aleo's record model and client-side proof generation. It handles aleo1-prefixed Bech32m addresses and signs zkSNARK transactions locally without exposing inputs to a server.
Wallet
Puzzle Wallet ships an alternative non-custodial client with a focus on private dApp interactions and developer tooling. It supports the snarkVM record model end-to-end and is one of the standard wallets Aleo dApps integrate against.
Wallet
Avail Wallet rounds out the three-wallet supported set, giving end users a third independent client implementation. Multiple wallets matter on a privacy chain because client diversity reduces the surface area for any single team to weaken privacy guarantees through implementation flaws.
Infrastructure
The official RPC at https://api.explorer.aleo.org/v1 and the AleoScan explorer at aleoscan.io form the canonical query layer. Because most state is encrypted, block explorers on Aleo reveal far less than EVM explorers do — they show transaction proofs and public state, not record contents.
Infrastructure
snarkOS and snarkVM are the open-source reference implementations of the Aleo node and execution layer. Builders writing Leo programs interact with them via the official developer docs at developer.aleo.org, which is the single best entry point for tooling, language reference and testnet onboarding.
| # | Protocol | Category | TVL |
|---|---|---|---|
| 1 | Pondo Protocol | Liquid Staking | $22.38K |
Aleo vs peers
Aleo's only direct peer in the privacy-chain category is Zcash, but the two systems answer different questions. Zcash is a fixed-supply privacy currency with a UTXO model and a Halo2 shielded pool; Aleo is a general-purpose programmable privacy L1 with zkSNARK execution at the smart-contract level. The peer-relative read is therefore less about TPS and more about scope of privacy.
| Chain | Block | Finality | TPS | TVL |
|---|---|---|---|---|
| Zcash | 1.3 min | 37.5 min | 5 | $1.47M |
| Aleocurrent | — | — | — | $0.00 |
Comparison insights
- Scope of privacy: Zcash limits zero-knowledge confidentiality to value-transfer UTXOs inside its shielded pool, with no general smart contracts. Aleo extends zkSNARK privacy to arbitrary programs written in Leo, which means confidential DeFi, sealed-bid mechanisms and private identity flows are possible natively rather than only via an external mixer.
- Consensus generation: Zcash inherits Bitcoin-style PoW with the Equihash algorithm, 75-second block time and ~2,250-second finality (around 30 confirmations). Aleo runs AleoBFT, a DAG-based PoS protocol that does not consistently publish block-time and finality figures but targets a 20,000 TPS theoretical ceiling — roughly 800x the 25 TPS theoretical maximum Zcash advertises.
- Launch and maturity: Zcash has been live since 2016-10-28 and has weathered nearly a decade of cryptographic upgrades, including the Sapling and Orchard transitions and the move to Halo2 proving. Aleo went live on 2024-09-19, so it is roughly eight years younger and carries the operational risks of an early-stage mainnet, including thin liquidity, limited audit history at scale and a still-forming validator set.
- TVL gap: Zcash currently has roughly 1.47 million USD of DefiLlama-tracked TVL via wrapped or staking constructs, while Aleo has only Pondo Protocol's roughly 22,375 USD liquid staking deployment. Neither is a meaningful DeFi hub by absolute TVL, but the size gap reflects how much later Aleo arrived and how nascent its DeFi surface is.
- Developer surface: Zcash offers no general smart-contract language, so building anything beyond shielded transfers requires sidechains or custom wallets. Aleo ships Leo, a purpose-built language compiling directly to zkSNARK circuits, plus snarkVM, snarkOS and a documented RPC at api.explorer.aleo.org/v1 — a much wider builder surface, at the cost of a steeper learning curve than a normal EVM environment.
Aleo timeline
Aleo's history is short and concentrated. The project began as academic research at Cornell, with foundational ideas drawn from the 2018 Zexe paper that formalized decentralized private computation using recursive zkSNARKs. The Aleo Systems team and the Aleo Network Foundation spent multiple years building snarkOS, snarkVM and the Leo language, running incentivized testnet phases that distributed early credits to community provers and validators. Mainnet launched on 2024-09-19, the single defining event in the chain's recorded timeline and the genesis from which all current state derives. Compared to the multi-incident histories of older networks — Solana's repeated mainnet outages, the BSC Token Hub bridge exploit of October 2022 in which an attacker minted roughly 566 million USD worth of BNB before validators paused the chain, or Ethereum's contentious DAO fork in 2016 — Aleo has no comparable major public incident, which is consistent with a sub-two-year-old chain operating at light load. That absence is not the same as a clean security record; it primarily reflects insufficient operational time and TVL to attract sophisticated attackers. Honest reporting on Aleo's history therefore must be modest: one canonical event (the 2024-09-19 mainnet launch), an ongoing process of validator-set decentralization, and a still-young economic and prover ecosystem. The most important historical questions about Aleo — how AleoBFT performs under adversarial load, whether the coinbase puzzle prover market reaches healthy decentralization, and whether the snarkVM trusted setup and circuit library hold up to extended audit pressure — will be answered over the next several years of mainnet operation, not before.
- 2024-09-19launchAleo mainnet launch
Developer reference
For developers, Aleo's onboarding surface is compact and well-documented. The official RPC endpoint is https://api.explorer.aleo.org/v1, the canonical block explorer is aleoscan.io and the documentation hub is developer.aleo.org. Addresses are Bech32m-encoded with an aleo1 prefix, so wallet integrations should not assume any EVM 0x-style address handling. The native token is ALEO and pays for gas, staking and coinbase puzzle rewards. The primary language is Leo, a Rust-flavored language that compiles directly to zkSNARK circuits rather than bytecode, which means loops and conditionals must be bounded and unrolled — a different mental model from Solidity. snarkVM is the execution engine and snarkOS is the reference node implementation; both are open source. Supported wallets for dApp integration include Leo Wallet, Puzzle Wallet and Avail Wallet. Client-side proof generation is a core architectural assumption, so dApps should plan for users to spend local compute on proving rather than relying on a relayer-side prover by default.
Assets swappable on Aleo
Grouped by category. Click any asset to open its swap page for a live quote.
Other
1 assets
Aleo settle-time comparison
Shorter bars mean faster confirmations. Real settle time also depends on network congestion — figures are indicative.
Aleo asset coverage comparison
Longer bars mean more assets are swappable on that chain.
Aleo FAQ
01Is Aleo a fully decentralized blockchain?
Aleo runs AleoBFT, a DAG-based proof-of-stake protocol with a coinbase puzzle proof-of-work prover layer on top. As a sub-two-year-old mainnet (live since 2024-09-19), its validator set and prover network are still maturing. The protocol design is permissionless, but operational decentralization metrics — validator count, geographic distribution and stake concentration — should be evaluated against current data rather than assumed from the design alone.
02What is Aleo's finality time and TPS?
Aleo's block time and instant finality figures from AleoBFT are not consistently published in the official spec, so the honest answer is that they are not yet publicly benchmarked. The published theoretical throughput ceiling is around 20,000 TPS, cited from AleoBFT upgrade announcements. Typical-load TPS on mainnet has not been independently benchmarked in production conditions.
03How is Aleo different from Zcash?
Zcash is a privacy-focused UTXO cryptocurrency with a Halo2 shielded pool and no general smart contracts. Aleo is a programmable privacy L1 where zkSNARK confidentiality extends to arbitrary programs written in Leo. Zcash launched 2016-10-28 and runs PoW Equihash; Aleo launched 2024-09-19 and runs AleoBFT DAG PoS. The two solve overlapping but distinct problems.
04Why does Aleo use zkSNARKs by default?
Aleo treats privacy as the default state model rather than an optional shielded pool. Every transaction is encoded as a zkSNARK proof, so inputs and state mutations are encrypted as private records while only the proof of correct execution is broadcast on-chain. Client-side proof generation keeps sensitive inputs on the user's device, which is structurally stronger than relayer-based privacy models.
05What wallets and tools support Aleo?
Aleo's supported wallet set includes Leo Wallet, Puzzle Wallet and Avail Wallet, all non-custodial browser extensions built natively for the snarkVM record model. The official RPC is https://api.explorer.aleo.org/v1, the canonical explorer is aleoscan.io and the developer documentation is at developer.aleo.org. Builders use Leo for contracts, snarkVM for execution and snarkOS as the reference node.