If you are sending
One signature, and you state the most you will pay. If no solver turns up, Circle pays you anyway at its own speed — Arcaidia makes the transfer faster, it is never required for it to arrive.
Official communiqué 04
One market, two speeds
You are paid in seconds by somebody else’s USDC. Circle’s transfer arrives minutes later and repays them, with a fee for the minutes they carried it. That gap is the entire business.
01 · You
You sign one intent
USDC in on Ethereum, the most you’ll pay, and who receives it on Arc. Nothing has moved yet.
02 · Router
The router commits it
Your USDC goes to Circle’s CCTP in the same transaction. If that handoff fails, the whole thing reverts and you keep your money.
03 · Fast path
A solver verifies and prices it
It re-reads your transaction on Ethereum itself, weighs free liquidity against what is already at risk, and signs a 45-second permission for one vault.
04 · Fast path
A vault advances the money
An LP’s USDC on Arc pays the recipient, seconds in. Asked for a token instead of USDC? The vault swaps it on Arc through Uniswap before delivery, and falls back to USDC if it cannot.
05 · Canonical
Circle settles, minutes later
Burn, attestation, mint. The settlement receiver verifies Circle’s message and releases the USDC to the vault that paid.
06 · Yield
The vault is repaid, with the fee
Principal plus fee land back in the vault, so every share is worth a little more than it was. That is the liquidity provider’s return — paid for carrying the minutes, not for taking a view.
If you are trading
The same intent, except you name the token you want on the far side. The vault swaps its USDC for it on Arc through Uniswap before delivery, and falls back to paying you USDC if the swap cannot fill. The provider’s risk stays denominated in USDC either way.
If you are providing liquidity
Deposit into any vault and hold its shares. The fee it charges rises with how much of it is already at risk, so the market prices its own scarcity:
- Under 50%10 bps
- 50 – 75%25 bps
- 75 – 90%60 bps
- Over 90%120 bps
Utilisation bands, set per vault at creation and immutable after it. The protocol keeps a configured share of each fee; the rest raises the share price.
Launch status
What the launch needs
The contracts are rewritten for mainnet and the rehearsal is written down. Three things stand between that and an open market, and two of them are money.
$20,000
An independent audit
An external firm reads the Solidity diff before any mainnet money moves. We closed nine blockers ourselves — one of them a double payment we reproduced from archive state and turned into a regression test. Finding our own bug is exactly why we are not the right people to sign off on our own fix.
$200,000
Vault capital on Ethereum and Arc
Seeds the house vault on both chains so the fast path can pay at a size worth using. The launch opens at 25 USDC per intent with a daily volume cap, and the cap only rises as the settlement record earns it. Capital is never custodial: it sits in an ERC-4626 vault its depositor can withdraw from.
One hire
A business development manager
Large market makers are the natural liquidity providers and solvers here — they already carry inventory across chains and price short-dated risk for a living. Getting Arcaidia in front of them is a relationship business, and it needs somebody whose job it is.
Already standing
- Contracts rewritten for mainnet: nine blockers closed, each with the regression test that proves it.
- Every external address — USDC, TokenMessenger, MessageTransmitter, on both chains — read from the chain itself rather than from a document.
- One deployment path for testnet and mainnet, with a read-only verifier and a wiring script that refuses to re-point a trust already set.
- The full gate green: contracts, every package suite, contract tests in both directions, and a golden end-to-end run across two chains.
- A written rehearsal: drain the old set, redeploy, verify, run the house vault alone, then a second vault competing against it.
Not yet
- No external audit has been commissioned. Until one has, treat the contracts as unaudited.
- Nothing is deployed to mainnet, and the testnet rehearsal has not been run end to end yet.
- Settlement is by proof of Circle's attestation, not trustless end to end — and an owner-held recovery path for stuck settlements still exists.
Total ask · $220,000 + one hire
Read the roadmap Open a vault on testnet
Auditing, market making, or the business development job itself — the repository is the fastest way to reach us, and the ten-stage walkthrough is the long version of the diagram above.