AZverse is the shared infrastructure — liquidity, matching, and settlement — that every Composition runs on. Its finality is verifiable offline, from open-source code, without trusting us. AZX, our flagship Composition, is where you trade on it.
Every claim below links to code you can read and run. Trust is a promise; these are receipts. The network settles on AZ, its own Layer 1 — and you can verify that settlement yourself.
AZ, the network's settlement Layer 1, ships an offline finality verifier. Feed it a run transcript and it independently confirms the quorum signatures and linked commit certificates — no AZverse endpoint in the loop.
az-bft · verify a transcriptThe consensus engine beneath the network is a weighted, two-chain HotStuff-family protocol with deterministic safety, pacemaking, reconfiguration and recovery — spec, safety rules and a deterministic devnet, all public.
Read the protocol specThe Solidity contracts behind AZ AssetVault are open to read and deployed on-chain — not a black box you have to take on faith.
asset-vault-contractsA documented public API with language demos. Anyone can integrate, audit behavior, or run the CLI tooling against the network.
api-docsAZverse is not an exchange — it's the open financial network that exchanges are composed on. Its mission is to Compose All Finance.
AZverse is the instrument; Composers are the ones who play it. The network provides the shared primitives — liquidity, matching, settlement — and a Composer arranges them into a Composition: a complete financial product under its own brand. AZ is the first Composer, and AZX is its flagship Composition.
Matching, risk, settlement, market data and APIs — one mature foundation, reused instead of rebuilt.
One deep orderbook, not many shallow ones. Every Composition draws on the same pool from day one.
Capabilities one Composer contributes become building blocks for the whole network — like BBX's tokenized-equity capability.
Trades on any Composition settle on the AZ Layer 1. Finality isn't a status message from a server — it's a set of signed certificates anyone can check.
Orders match on AZverse's shared orderbook (AZX is the flagship Composition) and are submitted to AZ for settlement.
Validators run az-bft's two-chain protocol, producing signed quorum certificates.
A linked commit certificate finalizes the block with deterministic safety.
The offline verifier confirms the certificate — independently, from source.
We won't tell you we're something we're not. Here is exactly what is open in the network today and what we're opening next — the boundary lives in the code, not in a marketing line.
Why we frame it this way. "Decentralized" is easy to write and hard to prove. We'd rather show you an open consensus engine, an offline finality verifier, and on-chain contracts — and be honest that the validator set is still permissioned — than claim a finish line we haven't crossed.
The core components of the network are public on GitHub. Traders can audit how settlement works; Composers can see the foundation they compose on. Start with az-bft.
BFT consensus engine for the AZ L1 — spec, safety rules, deterministic devnet, offline finality verifier.
On-chain Solidity contracts for AZ AssetVault.
Signer service that authorizes AZ AssetVault operations.
Documentation for the AZverse open API, with language demos.
Command-line tools for the AZverse network.
See the full AZverse organization on GitHub.
Traders can verify the network's finality from source. Composers can compose their own financial brand on the same open infrastructure.