Contracts

Every address Cowl runs on, with its ABI one click away. The full stack — shielded pool, proof verifiers, and the atomic trade adapter — is live on Robinhood Chain mainnet and testnet both. Read any of them on the explorer before you send a wei.

Robinhood Chain mainnet

The mainnet pool went live at block 18121312. Point an indexer or a cold sync there — nothing shielded exists before it. Trades route through the chain’s live Uniswap V3 stack, where the WETH/USDG book is over a thousand WETH deep.

Assets

Any ERC-20 on the chain can be shielded. What decides whether a spend can be gasless is whether the relayer can price its fee against the venue, which needs a route to the native asset.

Relayer endpoints

Each one publishes the chain and pool it serves, and its fee per spend. Check either with cowl relay quote <url>, or run your own.

Robinhood Chain testnet

Core

The pool went live at block 92522685. Point an indexer or a cold sync there — nothing shielded exists before it.

Trade venue

The testnet venue wears the exact Uniswap V3 interface the adapter targets — exactOutputSingle, quoteExactOutputSingle, same structs — so on mainnet the adapter points at the chain’s live V3 stack and nothing else changes. The test USDG mints openly: every install is its own faucet.

ABIs

Every ABI ships from this site as plain JSON — cowlprotocol.com/abi/<Contract>.json — ready for viem, ethers, or anything else that eats JSON:

import { createPublicClient, http } from "viem";

const POOL = "0x6f98666e9d05431dCd765AAa289a5E346AfA6a3E"; // mainnet
const abi = await fetch(
  "https://www.cowlprotocol.com/abi/ShieldedPool.json",
).then((r) => r.json());

const client = createPublicClient({
  transport: http("https://robinhood-rpc.publicnode.com"),
});

const root = await client.readContract({ address: POOL, abi, functionName: "root" });
const held = await client.readContract({
  address: POOL,
  abi,
  functionName: "pooledValue",
  args: [0n], // native coin — the per-token conservation cap, live
});

The pool’s events and their topic hashes are documented under onchain events; governance state — owner, timelock, conservation cap — is public and covered in the trust model.