Skip to content

Contracts on Arc

The contracts Vestiarion deploys and the Circle contracts it calls, with their addresses.

Vestiarion moves money on Arc through contracts of its own, its escrow and its spending limit in two versions, which each workspace deploys for itself, and through contracts Circle runs. The addresses below are on Arc testnet and open on its explorer; on Arc mainnet, a workspace that pays from its owner's wallet deploys its own spending limit contract, as VestiarionSpendingLimit says.

Vestiarion's contracts

They were written for Vestiarion and are not audited. Their source is in the repository's contracts/ folder, compiled with Solidity 0.8.37, the optimizer on at 200 runs, for the paris EVM version. A workspace that uses one gets its own copy, deployed through Circle's Smart Contract Platform from a deployer wallet of its own. The app shows the copy's address: the escrow's on Contractors → Milestone escrow, and the spending limit's, with the agent's wallet, on Treasury, under the agent's spending limit, On Arc.

VestiarionEscrow

Locks a milestone's USDC for a contractor before the work starts. See Lock a milestone in escrow.

  • Only the workspace's operating wallet, the payer, can call it.
  • fund(id, payee, amount, refundAfter) locks an amount for a payee. release(id) pays it to that payee. refund(id) returns it to the payer, and only from refundAfter. Each hold ends once, released or refunded.
  • It has no owner and cannot be upgraded.
  • It emits Funded, Released and Refunded.
  • An owner or admin deploys it with Set up escrow, signed in the ledger as escrow_deployed.

VestiarionSpendingLimit

Makes the agent's spending limit binding on Arc. See Enforce the limit on Arc.

  • The agent's payments leave the operating wallet through pay(to, amount, ref), and only through it: the agent's own wallet holds no money. The operating wallet approves the contract for what it may draw.
  • pay refuses anything past the daily figure (the current UTC day) or the 7-day figure (that day and the six before it), and pays each ref once.
  • Only its owner, the operating wallet, changes the figures, with setLimits. It cannot be upgraded.
  • It emits Paid and LimitsSet. spentToday() and spentThisWeek() read what it paid.
  • An owner or admin deploys it with Enforce on Arc, signed in the ledger as spending_limit_enforced.
  • On Arc mainnet, a workspace that pays from its owner's own wallet gets its copy from that wallet instead, which deploys it as the treasury and the owner, and approves it. Every payment from that workspace leaves through pay, including the ones people approve. See Path C: your own wallet.

VestiarionSpendingLimitV2

Version 2 of the spending limit contract, which a workspace paying from its owner's own wallet deploys since Oct 19, 2026. It does everything VestiarionSpendingLimit does, with the same pay, figures, events and errors, and also pays a vendor on another chain. See Pay a vendor on Base or Arbitrum from Arc mainnet.

  • payAcrossChains(amount, maxFee, domain, recipient, ref), for the agent only, counts amount + maxFee against both figures and marks ref paid, as pay does: a ref is paid once by either function.
  • It draws amount + maxFee from the treasury, approves CCTP's TokenMessengerV2 for it, and calls depositForBurnWithHook with fast finality and the forwarding hook, so Circle's Forwarding Service mints on the payee's chain. The payee is minted amount and whatever of maxFee the transfer does not charge.
  • TokenMessengerV2 and the CCTP domains it may burn for are fixed when it is deployed, from the network's payee chains then: on Arc mainnet Base (domain 6), and Arbitrum (domain 3) for one deployed since Oct 22, 2026; the CCTP testnets on Arc testnet. Any other domain is refused with DomainNotAllowed. Vestiarion reads allowedDomains() from the contract before offering a payee a chain.
  • maxFee may be at most 10% of amount and at most 2 USDC; above either, it refuses with FeeTooHigh.
  • It holds nothing after a call: its USDC balance must be what it was before, and its approval of TokenMessengerV2 back at 0, or the whole call reverts with BalanceLeft.
  • It emits PaidAcrossChains too, and VERSION() returns 2.
  • An owner upgrades a version 1 contract to it from Go live. See Upgrade your contract to pay other chains.

Deployed

Both run in production in testnet-2, our own test workspace:

ContractAddressDeployedDeploy transaction
VestiarionEscrow0x74af203fec3f121ff1cd3a763092d1211487702bOct 1, 20260x550727a6…1860
VestiarionSpendingLimit0x9da3c47f73ea9399ac566806a189b0bf47b7d4baOct 3, 20260xf48ee082…e4ff

The workspace's wallets around them:

WalletAddressWhat it does
Operating0x97f85033bbd83870a841cf7153f35b387746b6b6Pays invoices and buys USYC. The escrow's payer, and the spending limit's owner and the treasury it draws from.
Reserve0xa8a4ced0cda82b24d11e0386f066eb8c27fd4887Holds the USYC and sells it.
Agent0xa79bd77b00143ced32a81d1fb8215d7dca21526aCalls pay on the spending-limit contract. It holds no money.
Escrow deployer0x2590cc3c26f691af6b7203bd283eb055160a1a6cDeployed the escrow.
Spending-limit deployer0x10e8f32d53bdcae4b48cb391c0bb84374b7565f3Deployed the spending-limit contract.

Deployed on Arc mainnet

A spending limit contract runs on Arc mainnet in mainnet-wp, our own workspace there, which pays from a passkey wallet. The passkey wallet deployed it, set its figures and approved it in one transaction. Its figures, read from the contract: 50 USDC a day and 150 USDC in 7 days.

ContractAddressDeployedDeploy transaction
VestiarionSpendingLimit0xd90cA89Fc318d0330Bb14eaeF78B72C3CA7E7fB6Oct 7, 20260xe6261540…a9bb
WalletAddressWhat it does
Treasury0x49A0e31153562a81cdc79ACF6D138B1965F71631The passkey wallet. It holds the USDC and is the contract's owner and the treasury it draws from.
Agent0x67b278c94852F8C9058418d3F17C9A98F4B05D6CCalls pay on the contract. It holds only USDC for gas.

Its first payment, 0.10 USDC to a vendor on Oct 7, 2026: 0xcecef38e…dee6. USDC on Arc mainnet is 0x3600000000000000000000000000000000000000, the same address as on Arc testnet.

Verified source

Every contract Vestiarion has deployed is verified, so its explorer shows the source and anyone can check that the bytecode on chain was built from this repository. Each was submitted with the exact standard JSON input the app compiles with: one source keyed by its path in this repository, contracts/solc-settings.json, and Solidity 0.8.37 (0.8.37+commit.f401782d). On Sourcify both the creation and the runtime bytecode are an exact match, metadata included, and Blockscout, the explorer of both networks, shows the same source on each contract's page.

NetworkContractAddressDeployed forSourcify
Arc mainnetVestiarionSpendingLimit0xd90cA89Fc318d0330Bb14eaeF78B72C3CA7E7fB6mainnet-wp, Oct 7, 2026Exact match
Arc mainnetVestiarionSpendingLimitV20x00b83bA62F17cd49c9ccB8e782e166c481e5d94Four own workspace's first Arc mainnet payout to Base, Oct 19, 2026Exact match
Arc testnetVestiarionEscrow0x74af203fec3f121ff1cd3a763092d1211487702btestnet-2, Oct 1, 2026Exact match
Arc testnetVestiarionEscrow0xd74997e6e93e997437a543707e77f6662a1c9a9bOct 10, 2026Exact match
Arc testnetVestiarionSpendingLimit0x9da3c47f73ea9399ac566806a189b0bf47b7d4batestnet-2, Oct 3, 2026Exact match
Arc testnetVestiarionSpendingLimit0xdeb475145cd1982391083a8e7f306dde917f276eOct 10, 2026Exact match
Arc testnetVestiarionSpendingLimit0xdaf84b4aef1028bd3a4cd67d786253602437911aOct 15, 2026Exact match

A contract a workspace deploys later can be verified the same way: send Sourcify's POST /v2/verify/{chainId}/{address} the same standard JSON input, the compiler version above, the contract as contracts/<file>.sol:<name>, and its deploy transaction. Arc mainnet is chain 5042 and Arc testnet 5042002.

Circle's contracts Vestiarion calls

On Arc testnet:

ContractAddressWhat Vestiarion does with it
USDC0x3600000000000000000000000000000000000000Arc's USDC ERC-20 interface, 6 decimals: every payment, escrow lock and approval.
EURC0x89B50855Aa3bE2F677cD6303Cec089B5F319D72aPays invoices in EURC.
USYC0xe9185F0c5F296Ed1797AaE4238D26CCaBEadb86CCircle's tokenized money market fund, which the reserve wallet holds.
USYC Teller0x9fdF14c5B14173D74C08Af27AebFf39240dC105ABuys USYC with deposit, only in its daily window, and sells it with redeem, at any hour. mintPrice says whether buying is open.
USYC Entitlements0xCC205224862C7641930c87679E98999d23C26113Asked with canCall whether each wallet is allowlisted, before the reserve is turned on.
Gateway Wallet0x0077777d7EBA4688BDeF3E311b846F25870A19B9Holds the USDC the operating wallet deposits for Gateway payouts and the service budget.
Gateway Minter0x0022222ABE238Cc2C7Bb1f21003F0a260052475BMints a Gateway payout on the payee's chain, named in each burn intent.
CCTP TokenMessengerV20x8FE6B999Dc680CcFDD5Bf7EB0974218be2542DAABurns USDC for a payout to another chain. Circle's Forwarding Service submits the mint there.

A payee on another chain is paid in that chain's USDC:

Edit this page on GitHub (opens in a new tab)