Skip to main content
Every Caplane contract is deployed on two public testnets. Each address below links to its verified source on the explorer, so you can confirm every claim in these docs against the chain directly.

Robinhood testnet (chainId 46630)

The Allocation floor and the chain the Quickstart brokers on. Explorer: https://explorer.testnet.chain.robinhood.com.

Arbitrum Sepolia (chainId 421614)

Hosts the Timeboost adapter and the full adapter set. Explorer: https://sepolia.arbiscan.io.

USDC EIP-712 domain

The domain a consumer signs the EIP-3009 authorization under, and the token verifies against. The name, version, and verifyingContract are the same on both chains; the chainId differs, so the domain separator differs. The SDK builds this with domainFromRegistry(registry); never hard-code it.
FieldValue
nameTest USD Coin
version2
verifyingContract0x125959541Bb486058E7e3b55E49b3B04e49fBa5E
ChainchainIdDomain separator
Robinhood testnet466300xed726def0aa6e4f7047267d1ac97ce289cc2a22d05e84d86240639e575076378
Arbitrum Sepolia4216140x2ade651f27d81651130a289852ddb4a61d1c622d0c4dacf7b59f7753c9d8c3a4

Timeboost reference

The Timeboost adapter commits to inclusion in an Arbitrum express lane via the live ExpressLaneAuction at 0x991DbEDf388CB5925318f06362D4fCa7b040527D (Arbitrum Sepolia, 60-second rounds, reserve 1 wei). Inclusion is delivered off-chain via the el-proxy (timeboost_sendExpressLaneTransaction). See honest limits for why this is a generality proof, not a resale-demand claim.

Endpoints

The relayer and faucet are convenience services, not coordinators. The relayer is permissionless: run your own with one command (pnpm --filter @caplane/relayer start), or point at a hosted one. GET /info returns a relayer’s public feeBps floor. The faucet dispenses TestUSDC to an address you control. None of these holds your key or sits in the settlement path.

How these are sourced

Every address here comes from the deployment registry (deployments/<chain>.json) and is verifiable on the explorer. Addresses are never hard-coded into application code; the SDK resolves them from the registry. If these docs and the chain ever disagree, the chain is correct.