How Arcway moves capital.

Overview

Arcway unifies treasury visibility, capital intents, policy checks, member approval and execution into one interface. Smart contracts on Ethereum Mainnet are the source of truth; the app reads them directly and asks your wallet to sign every write.

Four contracts share the responsibilities:

• Treasury vault — custody, reservations, available balance, release and execution.
• Policy engine — allowed assets, max single SEND, quorum, approval threshold, execution delay and an optional destination allowlist.
• Action executor — the execution boundary. V1 supports SEND only.
• Arcway core — membership, the capital intent lifecycle, voting, finalization and execution.

The V1 flow

1. Fund. A member transfers USDC from their wallet to the treasury vault with a standard ERC-20 transfer.
2. Create intent. Define a SEND: amount, recipient, purpose and vote duration.
3. Policy check. The contract validates the intent and reserves the amount in the same transaction.
4. Vote. Each active member votes YES or NO once before the deadline.
5. Finalize. Anyone can finalize after the deadline. Quorum and approval are checked.
6. Delay. A passed intent becomes executable after the policy execution delay.
7. Execute. Anyone can execute; the vault sends the exact USDC amount to the recipient.
8. Verify. The UI waits for the receipt, shows it as Confirmed, links to Etherscan and refreshes once.

Treasury

The treasury shows three numbers: total (the vault's USDC balance), reserved (locked by active intents) and available (total minus reserved). New intents can only reserve available capital, so two intents can never promise the same funds.

Amounts use USDC's ERC-20 interface with 6 decimals. Failed intents release their reservation; executed intents consume it.

Capital intents

A capital intent is an immutable request: action (SEND in V1), asset (USDC), amount, recipient and purpose. Its lifecycle is Voting → Finalized → Passed / Failed → Delay → Executed.

The create form shows a read-only policy preview. The preview is guidance only: canonical enforcement happens in the contract, and the preview is never treated as authorization.

Policy engine

Policy is applied before governance. An intent that breaks a rule is rejected before any capital is reserved.

• Allowed assets — USDC in V1.
• Max single SEND per asset.
• Minimum quorum — how many members must vote.
• Minimum approval — the share of YES votes required, in basis points.
• Execution delay — time between passing and execution.
• Optional destination allowlist.

Approval & finalization

One member, one vote. Votes are public in V1. After the voting deadline anyone can finalize the intent: if quorum and approval are met it passes and its executable time is set; otherwise it fails and the reservation is released.

Execution & confirmation

Every onchain action moves through the same visible states:

Preparing → Wallet → Pending → Confirmed, plus Rejected by wallet, Reverted and Wrong network.

A transaction receipt means the transaction was included in a block. Arcway labels it Confirmed and links it on Etherscan. It is not labeled final: Ethereum consensus finality is a separate, later event, and V1 does not track finalized blocks.

Network

Network

Ethereum Mainnet

Chain ID

1

Gas asset

ETH

Treasury asset

Circle USDC · 6 decimals

USDC contract

0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

Explorer

Etherscan

View the USDC contract on Etherscan(opens in a new tab)

Gas is always paid in ETH. USDC is the treasury asset, never the gas asset. RPC endpoints are configured per environment.

No background infrastructure

V1 does not need a worker, listener, WebSocket subscription, cron job, database, indexer or polling loop. State is read directly from Ethereum when a page loads, when you press Refresh, and once after a confirmed transaction.

Current status

Arcway contracts are not deployed yet. The app currently shows clearly labeled preview data and cannot send transactions. No security audit is claimed.