Pre-funded USDC milestones · Arc Mainnet

Work funded. Payment proven.

Funds are locked before work begins and released only when proof meets the agreed terms. No promises. Just verifiable execution.

Arc at a glance

Money that carries a condition

Stablecoins solved how digital dollars move. This is what a digital dollar does when it stays committed until a milestone is submitted and accepted.

01

0% platform fee

USDC goes straight through

02

One vault per milestone

Isolated, auditable accounting

03

<1s settlement finality

Arc mainnet · chain 5042

04

Rule-bound vault

No operator keys, no seizure

Core guarantee

One rule for each side, written before work starts

The contractor never starts unfunded. The client never pays unproven. Both promises live in the same vault, and neither side can move the money alone.

Contractor

Do not start work until the money exists.

Open the shared link, read the vault balance onchain, and start only when the state says FUNDED. No unfunded milestones, no unpaid assessments.

Do not release money until the work is submitted.

The client commits the amount without paying it. The vault holds it, the contractor can prove it, and release happens only against a submitted deliverable — or by a review window the client pre-agreed to.

Vault balanceamount committed
Scopekeccak256 commitment
Release ruleapproval · review timeout

Release follows agreed rules, not promises.

Client approval releases instantly. If the client goes silent after a valid submission, the pre-agreed review window ends in a deterministic release. If the contractor never submits, the client reclaims after the deadline.

A disagreement cannot silently drain the vault.

Raising a dispute pauses the timeout release. In V1 a dispute ends only by client approval or a bilateral mutual cancel. No administrator, no platform key, no seizure function exists in the contract.

Process

Why Commit?

One primitive, three irreversible steps. Money is committed, work is proven, and settlement is executed by code — every step a verifiable transaction on Arc.

A milestone, step by step1 / 3
  1. 01

    Commit

    FUNDED

    The client deploys a milestone vault and moves the exact USDC amount into it. Immutable amount, parties and deadlines.

  2. 02

    Prove

    SUBMITTED

    The contractor submits the deliverable URL and its hash onchain. The review clock starts, deterministic from the chain timestamp.

  3. 03

    Settle

    SETTLED

    Approval or review-window timeout releases USDC to the contractor. No submission before the deadline refunds the client.

Honest boundaries

What V1 does not promise

Commit is narrow on purpose. These limits are shown to both parties before funding — never buried.

Work quality stays human

The vault guarantees funding and settlement rules, not that the deliverable is objectively good.

No third-party arbitration

A dispute freezes the timeout. V1 resolves it by approval or mutual cancel, nothing else.

Not a licensed escrow

Descriptive language only: pre-funded milestone, conditional payment, rule-bound vault.

Capability matrix

Built for work that already has a client

No marketplace, no discovery, no reputation game. Just the payment commitment around an agreement you already made.

  • Payment assurance, not just transfers

    The committed amount is provably locked before work begins.

  • Deterministic exits

    Review timeout for the contractor, deadline refund for the client.

  • Rules before conflict

    Amount, parties, deadlines and review window are immutably fixed at creation.

  • No custody by us

    Funds live in a contract vault controlled only by encoded rules.

Arc

USDC-native gas, sub-second finality, EVM equivalent.

Circle USDC

Settles through the native ERC-20 interface on Arc.

Foundry / EVM

74 contract tests, no upgradeability, no admin backdoor.

Wallets

MetaMask, Rabby, Coinbase Wallet, Rainbow.

commit.app/milestone?address=0x7a3f…1c2e

Spotlight

Every state change leaves a verifiable transaction.

Funding, submission, revision, dispute, release and refunds are all onchain events with a transaction hash, visible from the shared milestone link. The UI reads the vault directly — there is no backend that can lie about the money.

Community

Build in the open

The contract, the app and the deployment evidence are published for the Arc microgrant submission. Follow along or reach out.

GitHubsoonpublic repo at submission
X / Twittersoonbuilder profile at submission
Farcastersoonbuilder profile at submission