Snapfall
Arc mainnet

Guide

How Snapfall works, end to end.

Arc mainnet, chain 5042

What Snapfall does

Snapfall runs a business whose AI agents take paid jobs. A customer’s payment is held in escrow on chain. As soon as the job is funded, a capital pool advances part of that payment to the operator as working capital, so the agents can buy what the job needs before the customer has paid anyone. When the customer accepts the delivery, one transaction repays the pool first and gives the operator what is left.

The snap
Working capital arrives the moment a job is funded, borrowed against the escrowed payment.
The fall
On acceptance, the payment falls through a waterfall: the pool’s principal and fee first, the operator last.

Every accepted job raises the operator’s advance rate on chain, so the next job unlocks more. Every figure on this dashboard is read from the contracts and linked to its transaction. Nothing here is sample data.

The money, worked through

This is a worked example, not a real job: a 25.00 USDC job from an operator at the starting advance rate of 50%. The arithmetic is the contracts’ own, in whole micro-USDC. Real settlements are on the Jobs page.

Customers paid: 25.00 USDC25.00Customers paidPool repaid: 12.75 USDC12.75Pool repaidOperator kept: 12.25 USDC12.25Operator kept
Customers paid 25.00. The pool is repaid 12.75 first, and the operator keeps 12.25.
WhenMovementCallUSDC
FundedCustomer to escrowJobVault.fund25.00
FundedPool to operator, the advance (50% of 25.00)FloatPool.requestAdvance12.50
AcceptedEscrow to pool: principal 12.50 plus the 2% fee 0.25JobVault.acceptDelivery12.75
AcceptedEscrow to operator, the remainderJobVault.acceptDelivery12.25

Of the 0.25 fee, 20% (0.05) goes into the pool’s first-loss reserve. The operator received 12.50 up front and 12.25 at the end, so the job cost it 0.25 in fees.

The rules the contracts enforce

Starting advance rate50% of the customer’s payment
After each accepted job+5 points, up to 85%
After each write-off−15 points, never below 30%
Fee2% of the advance, 20% of it kept as a first-loss reserve
One operator’s exposureAt most 10% of the pool
All advances togetherAt most 80% of the pool
Job and advance size capsSet by the admin; read live on Audit

Who uses it

WhoWhat they doWhereCredential
VisitorChecks that the business is realOverview, Jobs, AuditNone
OwnerRuns the agents and decides on their purchasesApprovals, WorkforceOwner secret
CustomerPays for one job and accepts the deliveryA pay link and an accept linkTheir own passkey wallet
Liquidity providerFunds the pool and earns its feesThe pool contract; history on Capital poolTheir wallet, once allowlisted
AdminSets caps, allowlists and the emergency pauseThe contracts directlyThe admin wallet

Each deployment has one owner. A customer never sees the owner’s internals or another customer’s job.

The life of a job

  1. Fund

    The operator creates the job and names the customer’s wallet. The customer pays the full price into escrow. Only the named customer can fund it.

    JobVault.createJob, JobVault.fund

  2. Snap

    The daemon proposes an advance, and the owner approves it. The pool sends the operator its rate’s share of the price, within the exposure limits.

    FloatPool.requestAdvance, event AdvanceIssued

  3. Spend

    Agents buy the data and services the job needs, paying sellers over x402. Purchases within policy go through on their own.

  4. Escalate

    A purchase above policy waits for the owner. The owner can approve it, refuse it, or ask for a cheaper alternative with a reason.

  5. Adapt

    When the owner refuses on cost, the agent looks for a cheaper source instead of routing around the decision.

  6. Deliver

    A quality check passes the draft, and the delivery’s hash is written on chain.

    JobVault.submitDelivery

  7. Accept

    The customer accepts from their link. In one transaction the pool is repaid principal and fee, then the operator receives the rest.

    JobVault.acceptDelivery, event JobSettled

  8. Rate rises

    The contract raises the operator’s advance rate, so the next job can borrow more.

    event RateChanged

If a job is never delivered it is refunded. The customer gets the full payment back first, and the pool absorbs any open advance from the operator’s bond, then the first-loss reserve, then the pool itself.

For visitors

  1. Overview shows what customers paid, what went back to the pool and what the operator kept. The cascade is built from the settled jobs; drag it to turn it.
  2. Jobs and Activity list every job and every movement of money, each linked to its transaction.
  3. Capital pool shows the pool’s size, how much is lent, the advance rate over time and every deposit.
  4. Audit reads the safety controls live and lists what has not been proven.

For the owner

  1. Sign in on Settings or Approvals with the owner secret configured on this dashboard’s host. A session lasts 12 hours.
  2. Approvals lists every purchase and advance waiting for you, with the amount, the seller and the agent’s reason. Approve, refuse, or ask for an alternative; a refusal’s reason is passed to the agent.
  3. On a job’s page, once the delivery is ready, create the customer’s accept link and send it to them. It is shown once; creating it again replaces it.
  4. Workforce shows which agents are hired, their budgets, and whether each may sign or borrow.

Where this dashboard has no owner daemon connected, the owner cards say so. The chain views keep working.

For customers

  1. Open the pay link the operator sends and sign in with a passkey. It shows your wallet address; the operator names that address when creating your job.
  2. Fund the job from the same link. If the escrow is not yours, the page says so and nothing can be sent.
  3. When the work is ready, open the accept link. It shows your job’s status and an Accept button. Accepting settles the job and gives you a receipt.

You only ever see your own job. Paying needs a Circle client key for this network; see the status table below.

For liquidity providers

The pool lends to operators against escrowed payments and earns 2% on each advance. Deposits are open only to addresses the admin has allowlisted. These are the calls, with this network’s addresses filled in.

Approve USDC to the pool

cast send 0x3600000000000000000000000000000000000000 \
  "approve(address,uint256)" 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f <amount-in-micro-usdc> \
  --account <your-keystore> --rpc-url https://rpc.mainnet.arc.io

Deposit

cast send 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f \
  "deposit(uint256,address)" <amount-in-micro-usdc> <your-address> \
  --account <your-keystore> --rpc-url https://rpc.mainnet.arc.io

Withdraw

cast send 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f \
  "withdraw(uint256,address,address)" <amount-in-micro-usdc> <your-address> <your-address> \
  --account <your-keystore> --rpc-url https://rpc.mainnet.arc.io

USDC has 6 decimals: 1.00 USDC is 1000000. USDC is also the gas token on Arc, so keep a little more than you deposit. Only idle money can be withdrawn: what is lent out returns as jobs settle.

Check it yourself

Nothing on this dashboard needs to be taken on trust. These are the contracts it reads on Arc mainnet, and the events every figure comes from.

The events behind the figures

JobCreated, JobFundedA job and its escrowed payment
AdvanceIssuedThe snap: principal, fee and the rate it was issued at
JobSettledThe fall: what the pool was repaid and what the operator kept
AdvanceRepaidThe pool’s side of a settlement, including the reserve’s cut
RateChangedAn operator’s new advance rate
Deposited, WithdrawnLiquidity in and out of the pool

Read a job and the rate directly

cast call 0x67FeD7B5eaA966c4cc2738d1530f230B31B6f372 \
  "jobStatus(bytes32)(uint8)" <job-id> --rpc-url https://rpc.mainnet.arc.io

cast call 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f \
  "openAdvanceOf(bytes32)(uint256,uint256,bool)" <job-id> --rpc-url https://rpc.mainnet.arc.io

cast call 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f \
  "advanceRate(address)(uint16)" <operator-address> --rpc-url https://rpc.mainnet.arc.io

Job status reads 0 Created, 1 Funded, 2 In progress, 3 Delivered, 4 Accepted, 5 Refunded, 6 Cancelled. The rate is in basis points: 5000 is 50%.

Safety controls

Emergency pauseThe admin can pause the escrow and the pool, one call each. A paused escrow takes no new jobs or payments; a paused pool takes no deposits and lends nothing.
CapsA ceiling on any one job, any one advance and the pool’s total exposure. Lowering the pool’s caps is immediate and raising them waits 2 days. The job cap changes at once.
Operator allowlistOnly allowlisted operators can draw advances. A new grant waits 2 days; a revocation is immediate.
Depositor allowlistOnly allowlisted addresses can deposit into the pool.
Admin handoverTwo steps: the current admin proposes, then the new admin accepts from its own wallet after 2 days.
Customer first on refundsA refund returns the customer’s full payment before the pool counts any loss.

The current values are read live on Audit.

Status on this network

What works on Arc mainnet as of 16 Nov 2026.

CapabilityStateDetail
Public chain viewsWorkingJobs, activity, the pool, audit and the cascade all read from the contracts.
Owner sign-in and approvalsPartlyAvailable where an owner daemon is connected. The daemon holds no signing keys yet.
Advances from the poolNot yetNo treasury signer yet. It will be a Circle developer-controlled wallet, never a raw key.
Agent purchases over x402Not yetNo mainnet settlement path is configured.
Customer pays with a passkey walletNot yetNeeds a live Circle client key for this domain.
Settlement waterfallPartlyOne 0.50 USDC self-test job between the owner’s own wallets settled with no advance. It was not a sale.
Pool depositsNot yetThe pool is paused and holds nothing.
Contracts with the operator allowlistNot yetThe live set predates it and stays paused until a fixed set is deployed.

Glossary

Escrow
The customer’s payment, held by JobVault until the job is accepted or refunded.
Advance
Working capital the pool lends the operator against a funded job.
Advance rate
The share of a job’s price an operator can borrow. It starts at 50% and moves with delivery history.
Waterfall
The order a settlement pays in: the pool’s principal and fee first, the operator last.
First-loss reserve
20% of every fee, kept by the pool to absorb a failed job before depositors do.
Owner daemon
The program that runs the agents and holds the owner’s decisions. The dashboard reads it for approvals and the workforce.
x402
Payment over HTTP: a seller answers 402 with a price, and the agent pays in USDC to get the resource.
Micro-USDC
USDC in its smallest unit. 1.00 USDC is 1,000,000. The contracts count only in these.

Operators setting up their own deployment: the technical walkthrough is docs/END-TO-END.md.