Risk Disclosure

Arc is Circle's private mainnet. The canonical routes for USDC to enter and leave the network are gated to a whitelist that Circle controls and can change at any time. This has direct consequences:

• funds on Arc may not be freely bridgeable out through canonical routes until Circle opens them — plan on the assumption that value on Arc can be illiquid;
• the premium at which Arc USDC trades against Base USDC exists because of this gate. If Circle opens the routes, the premium can collapse toward parity rapidly and without warning;
• Circle can pause, change, or discontinue network access policies with no involvement from us.

You should only commit an amount you are entirely willing to lose. There is no insurance, no deposit protection, no compensation scheme, and no counterparty who will make you whole. BRC in particular is a volatile asset whose realistic downside is zero.

You control your own wallet and keys, and every transaction you sign is irreversible once confirmed. Nobody — not us, not the contract, not the network — can reverse, cancel, or refund it. A single mis-typed address, a wrong token, or an accidental approval can cause permanent loss.

Prices come entirely from on-chain liquidity. When a pool is small, your own trade moves the price against you — sometimes dramatically. Buying pushes the price up as you buy; selling pushes it down as you sell. The larger your order relative to the pool, the worse your average price.

The price impact figure shown before a trade is an estimate. A pool that looks liquid on a chart can be very thin in practice.

Being able to buy does not imply you will be able to sell at a comparable price. If the buyers disappear, a displayed market value is a theoretical number, not money you can realise. Selling a large position into a thin pool can return a small fraction of what the displayed value suggests.

Between the moment you see a quote and the moment your transaction is included in a block, other trades can change the pool. Slippage tolerance protects you from receiving far less than expected by causing the transaction to revert instead — but a reverted transaction still costs gas, and setting a very high tolerance exposes you to a much worse execution price.

Pending transactions may be visible to others before they are included in a block. Automated bots can react to yours — buying just before it and selling just after, so that you receive a worse price. This behaviour is common on public networks and is not something the interface can prevent.

A liquidity position converts your deposit into both pool assets and rebalances between them as price moves. If price exits your chosen range, you end up holding only the less valuable side, and the fees you earned may not cover the difference versus simply holding. This is called impermanent loss, and with concentrated ranges it is amplified:

• tighter ranges earn more fees per dollar but fall out of range sooner;
• an out-of-range position earns nothing until price returns or you rebalance — rebalancing realises the loss;
• providing liquidity to a volatile asset against a stable asset means your range choice is an active price view, not a passive deposit.

Everything here runs on smart contracts: the pools, the router, the position manager, Circle's bridge contracts, the Wormhole core contracts, and the USDC Market escrows. No non-trivial software is free of defects. Bugs, exploits, economic attacks, or unexpected interactions between contracts can result in partial or total loss of funds, including funds held in escrow or liquidity positions.

You should not assume any code has been audited unless a specific audit report is published and you have read it.

The Bridge depends on Circle's infrastructure end to end:

• a lane that Circle has not enabled cannot complete transfers, no matter what you or we do — deposits and approvals made in advance sit waiting until the lane opens;
• attestation can be delayed by Circle's services; finality windows on the source chain (minutes on some chains) apply before attestation begins;
• if our relayer is offline, the final mint is not submitted automatically — a manual mint path exists, and on the reverse direction you pay the destination gas yourself;
• a burn executed into a lane that cannot attest would strand the funds; the interface refuses to hand out burn calldata while a lane is disabled, but you should never bypass those guards through other clients unless you understand exactly what you are doing.

The USDC Market settles by cross-chain proof: escrow on Arc is released only against a Wormhole guardian-signed proof of the Base-side payment. This design removes custodial trust, but it has its own failure modes:

• settlement depends on the Wormhole guardian network reaching its signing quorum; guardian outages delay settlement;
• our keeper reserves offers and relays claims. It cannot steal escrow, but if it misbehaves or goes down, trades can be delayed until timeouts allow self-serve recovery;
• sellers' escrow is refundable by timeout if no payment arrives — until that timeout passes, the escrowed funds are locked;
• the premium you pay or receive is a market price, not an oracle rate. It can move against you between quote and fill.

Arc USDC and Base USDC are both canonical USDC, but while Arc's exit routes are gated they trade at different prices. Buying Arc USDC at a premium is a bet that the premium persists or that you can deploy the funds on Arc at better than the premium you paid. If access policy changes, the premium can vanish. USDC itself carries issuer and reserve risk that is outside the scope of this interface.

Trading requires granting contracts permission to move tokens from your wallet. Approvals persist after the trade until you revoke them, and an approval granted to a malicious contract can be used to drain the approved token later. Review every approval request, prefer limited amounts where your wallet supports it, and periodically revoke approvals you no longer need.

Copies of this interface may be hosted on look-alike domains to capture signatures or seed phrases. Check the domain before connecting. We will never ask for your seed phrase or private key, never send you a direct message asking you to "verify" a wallet, and never ask you to sign a message to "unlock", "migrate", or "claim" funds.

Be especially careful with signature requests that are not plain transactions — a signature can authorise a transfer (or a Gateway burn intent) without looking like one. Only sign burn intents through flows you initiated yourself.

Prices, quotes, balances, order books, supply figures, and block heights shown here are derived from public blockchain data by our own reads and indexing. They can be delayed, incomplete, or wrong — because of a lagging scan, an RPC failure, a chain reorganisation, or a bug. Treat every number as a signal, never as the sole basis for a decision.

The interface depends on the Arc and Base networks, RPC providers, Circle's APIs, the Wormhole guardian network, price data sources, and hosting that we do not fully control. Congestion can delay or fail transactions. Chain reorganisations can undo recently displayed activity. Outages can make the interface unreachable or show stale data.

Your funds always remain in your wallet or in public contracts, regardless of whether this website is working.

Pool fees taken on each swap, bridge fees deducted from transfers, market fees on fills, and the network gas you pay are all non-refundable once a transaction is confirmed. Gas is consumed even by transactions that fail or revert, including trades rejected by your own slippage setting.

The legal treatment of crypto assets differs by jurisdiction and changes over time. Tokens could be treated as securities or other regulated instruments where you live. Rules that change after you buy can affect your ability to trade or hold. You are responsible for complying with the laws that apply to you and for reporting and paying any taxes you owe.

Nothing in the interface is financial, investment, legal, or tax advice, nor a recommendation or solicitation. Statistics, APRs, order books, and progress figures are mechanical results of on-chain data, not opinions about quality. Every decision is yours alone.

• Did you verify the contract addresses against the docs page?
• Is the pool deep enough that your order will not move the price badly?
• Have you checked the price impact and minimum received on the quote?
• For the bridge: is the lane you need actually enabled, and do you understand the finality wait?
• For the market: do you understand the premium you are paying and the refund timeout on escrow?
• Could you accept losing this entire amount without it mattering to you?
• Are you on the correct domain, with the correct network selected?

If any answer is no, the safe action is to not transact.