Which chains is Anoma on?

Anoma's deployment file lists the Protocol Adapter on a set of EVM mainnets and on two testnets, Base Sepolia and Ethereum Sepolia. This explorer indexes every one of those mainnets, and Networks lists them with their contract addresses and live status.

What is the Anoma Protocol Adapter contract address?

There is one adapter per network, so the address depends on the chain: Ethereum and BNB Chain each have their own, and the other mainnets share one of two addresses. Take it from Networks or /api/v2/networks, which hold the same mainnet addresses as Anoma's deployment file. The contract links on Anoma's Protocol Adapter docs page for Ethereum, Arbitrum and Base point to different addresses, so check which one you are looking at.

Does this explorer index Anoma testnets?

No. The adapters on Base Sepolia and Ethereum Sepolia are shown on Networks as deployed but not indexed, and /api/v2/networks returns them with testnet set to true and status set to deployed. On 23 October 2026, explorer.anoma.net/networks also marked both as not indexed.

How can I check the counts myself?

The counters are public read functions on each adapter, defined in Anoma's contract code, so a block explorer's contract read tab or a plain RPC call returns commitmentCount() and the others. This explorer's latest readings, with the block each was read at, are on Proof and at /api/v2/proof, and the separate Etherscan coverage audit is at /api/v2/explorer/integrity. To check one settlement by hand, see how to verify an Anoma transaction.

Is Gnoma Explorer the official Anoma explorer?

No: Gnoma Explorer is independent and not affiliated with the Anoma Foundation or Heliax. Anoma's official explorer is explorer.anoma.net, which Anoma's docs describe as showing indexed activity across existing Protocol Adapters, with a GraphQL Playground. How the two compare is set out in Gnoma and explorer.anoma.net.

Guide · updated 2026-10-24

Where Anoma is deployed: networks and contracts

Anoma reaches existing blockchains through one contract on each network, the Protocol Adapter. This guide shows where Anoma has deployed it, the address on each network, what this explorer means by "checked against the contract", and where the AnomaPay app is live.

What the Protocol Adapter is

The Protocol Adapter, often shortened to PA, is the smart contract that brings Anoma to a blockchain that already exists. Anoma's docs say it implements the Anoma DOS (Anoma's Distributed Operating System) on that base chain, so users, developers and applications can use the Anoma Resource Machine (ARM, the virtual machine at the heart of Anoma) without making any changes to the chain. Anoma's contract repository, pa-evm, describes it as a contract written in Solidity for settling ARM transactions on EVM-compatible chains. AnomaPay's docs add that it is deployed on every chain AnomaPay supports, controls shielded funds through forwarder contracts, and verifies the proofs that authorize transfers; the architecture page adds that it then settles the transaction. This explorer calls one transaction completed through the adapter a settlement, the word pa-evm itself uses for the adapter's job. [1] [2] [3] [4] [5] [6]

Which chains Anoma is on, and the contract addresses

Anoma publishes its own list of adapter deployments in the pa-evm repository: a file that maps each supported network to one contract address, testnets included. The table below lists the networks this explorer indexes, built from its chain registry, which holds the same addresses as that file. Each address opens its page here, which marks it as a Protocol Adapter and links to the settlement list of each network that uses it. Some networks share one address, but the file records a deployment on each network, and this explorer reads and checks each network on its own. Live status, gas and totals for every network are on Networks, and the registry is also served as JSON at /api/v2/networks. [1]

Network	Chain id	Protocol Adapter	Version
Ethereum	1	0x0ea3b55b68a3f307c8fe3fe66e443247c95f0cff	v1.1.0
BNB Chain	56	0xfc44b66a39fe6923ad8d3c93bfec369728862b68	v1.1.0
Base	8453	0x094fcc095323080e71a037b2b1e3519c07dd84f8	v1.1.0
Arbitrum One	42161	0x094fcc095323080e71a037b2b1e3519c07dd84f8	v1.1.0
OP Mainnet	10	0x094fcc095323080e71a037b2b1e3519c07dd84f8	v1.1.0
Aurora	1313161554	0x2D2Fa19aFdbb20DC73737ca5f075cfAE00Cd90C2	v1.1.0
MegaETH	4326	0x2D2Fa19aFdbb20DC73737ca5f075cfAE00Cd90C2	v1.1.0
Monad	143	0x2D2Fa19aFdbb20DC73737ca5f075cfAE00Cd90C2	v1.1.0
Stable	988	0x2D2Fa19aFdbb20DC73737ca5f075cfAE00Cd90C2	v1.1.0

What "checked against the contract" means

Each adapter keeps exact running totals in its own storage, a source that neither this explorer nor any data provider controls. In Anoma's contract code, creating a resource (Anoma's basic unit of state, which can stand for a token, a message or other data) adds its commitment to a commitment tree, and consuming one adds its nullifier to a nullifier set. commitmentCount() and nullifierCount() return how many of each the contract holds. The tree starts with one root for the empty tree, and each transaction that changes state stores one more, so commitmentTreeRootCount() minus one is the number of such settlements. latestCommitmentTreeRoot() returns the newest root, a value computed from every commitment so far. Every few minutes, in rotation, this explorer reads those values at the block its index has reached and compares them with what it has indexed up to that block. A network shows as verified when both counts are equal and the contract's latest root matches one of the newest indexed settlements. If no node still serves the contract's state at that block, the newest block is read instead, and while the index is more than a few minutes behind it, only agreement counts as a result. A difference must appear in three checks in a row before it is reported as a mismatch, so a settlement landing between two reads is not mistaken for missing data. The results are on Proof, beside the shielded pool and XAN checks. [1] [2] [3] [4] [5] [6] [7]

How Anoma's own lists compare

Anoma's sources do not all list the same networks. The Protocol Adapter page of Anoma's docs, last updated on 18 February 2026, names four mainnets: Ethereum, Arbitrum, Base and Optimism, which this explorer calls OP Mainnet. Anoma's blog announced BNB Chain later, on 1 April 2026. On that docs page, the contract links for Ethereum, Arbitrum and Base open addresses that differ from Anoma's pa-evm deployment file; the Optimism link matches it. Anoma's official explorer lists every network in that file. On 23 October 2026, explorer.anoma.net/networks and explorer.anoma.net/contracts marked Optimism, Stable and the two testnets, Base Sepolia and Ethereum Sepolia, as "not indexed here". This explorer indexes every mainnet in the file and neither testnet. A testnet is a practice network whose tokens carry no value; both testnet adapters appear on Networks as deployed but not indexed. Where explorer.anoma.net does more: it is Anoma's own explorer; its Contracts page names the adapter release, contracts/v1.1.0, with a link to the pa-evm repository; and Anoma's docs say it includes a GraphQL Playground for running queries against its index and lets a user configure networks and RPC endpoints, which this explorer does not offer. [1] [2] [3] [4] [5] [6]

Network	Anoma docs, Protocol Adapter page	explorer.anoma.net, 23 October 2026	AnomaPay, per Anoma's docs and blog	Gnoma Explorer
Ethereum	Listed	Indexed	Live	Indexed
BNB Chain	Not listed	Indexed (as BSC)	Live	Indexed
Base	Listed	Indexed	Live	Indexed
Arbitrum One	Listed (as Arbitrum)	Indexed	Live	Indexed
OP Mainnet	Listed (as Optimism)	Not indexed here (as Optimism)	Not listed	Indexed
Aurora	Not listed	Indexed	Not listed	Indexed
MegaETH	Not listed	Indexed	Not listed	Indexed
Monad	Not listed	Indexed	Live	Indexed
Stable	Not listed	Not indexed here	Live	Indexed
Base Sepolia (testnet)	Not listed	Not indexed here	Not listed	Deployed, not indexed
Ethereum Sepolia (testnet)	Not listed	Not indexed here	Not listed	Deployed, not indexed

Where AnomaPay is live

AnomaPay is a private payments network and app built on Anoma, for shielded transfers of ERC-20 tokens on EVM chains. Putting tokens into its shielded pool is what this explorer calls a shield; AnomaPay's docs call it a deposit. Those docs list AnomaPay as live on Ethereum Mainnet, BNB Smart Chain, Arbitrum, Monad and Stable. Anoma's blog announced the full public app on Base on 26 August 2026, after an invite-only beta there. So the adapter is deployed on more networks than AnomaPay is listed on: the Anoma pages read for this guide do not name AnomaPay on OP Mainnet, Aurora or MegaETH. The adapter is open to any application built on the ARM, so settlements on a network do not by themselves show that AnomaPay runs there. Resource logics profiles the programs behind each settlement from what they do on-chain, and External calls lists each shield and unshield with its token and network. [1] [2] [3] [4]

Questions

Which chains is Anoma on?: Anoma's deployment file lists the Protocol Adapter on a set of EVM mainnets and on two testnets, Base Sepolia and Ethereum Sepolia. This explorer indexes every one of those mainnets, and Networks lists them with their contract addresses and live status.
What is the Anoma Protocol Adapter contract address?: There is one adapter per network, so the address depends on the chain: Ethereum and BNB Chain each have their own, and the other mainnets share one of two addresses. Take it from Networks or /api/v2/networks, which hold the same mainnet addresses as Anoma's deployment file. The contract links on Anoma's Protocol Adapter docs page for Ethereum, Arbitrum and Base point to different addresses, so check which one you are looking at.
Does this explorer index Anoma testnets?: No. The adapters on Base Sepolia and Ethereum Sepolia are shown on Networks as deployed but not indexed, and /api/v2/networks returns them with testnet set to true and status set to deployed. On 23 October 2026, explorer.anoma.net/networks also marked both as not indexed.
Is AnomaPay available on every network where Anoma is deployed?: No. AnomaPay's docs list Ethereum, BNB Smart Chain, Arbitrum, Monad and Stable, and Anoma's blog added Base in August 2026. The adapter is open to any application built on the ARM, and Anoma's docs name AnomaPay as one such application; the adapter is deployed on more networks than AnomaPay is listed on.
How can I check the counts myself?: The counters are public read functions on each adapter, defined in Anoma's contract code, so a block explorer's contract read tab or a plain RPC call returns commitmentCount() and the others. This explorer's latest readings, with the block each was read at, are on Proof and at /api/v2/proof, and the separate Etherscan coverage audit is at /api/v2/explorer/integrity. To check one settlement by hand, see how to verify an Anoma transaction.
Is Gnoma Explorer the official Anoma explorer?: No: Gnoma Explorer is independent and not affiliated with the Anoma Foundation or Heliax. Anoma's official explorer is explorer.anoma.net, which Anoma's docs describe as showing indexed activity across existing Protocol Adapters, with a GraphQL Playground. How the two compare is set out in Gnoma and explorer.anoma.net.

Sources

Gnoma Explorer is independent and not affiliated with the Anoma Foundation or Heliax. Statements about Anoma are Anoma's own, from the sources above; figures are this explorer's, from the pages linked in the text.