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.
| When | Movement | Call | USDC |
|---|---|---|---|
| Funded | Customer to escrow | JobVault.fund | 25.00 |
| Funded | Pool to operator, the advance (50% of 25.00) | FloatPool.requestAdvance | 12.50 |
| Accepted | Escrow to pool: principal 12.50 plus the 2% fee 0.25 | JobVault.acceptDelivery | 12.75 |
| Accepted | Escrow to operator, the remainder | JobVault.acceptDelivery | 12.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 rate | 50% of the customer’s payment |
|---|---|
| After each accepted job | +5 points, up to 85% |
| After each write-off | −15 points, never below 30% |
| Fee | 2% of the advance, 20% of it kept as a first-loss reserve |
| One operator’s exposure | At most 10% of the pool |
| All advances together | At most 80% of the pool |
| Job and advance size caps | Set by the admin; read live on Audit |
Who uses it
| Who | What they do | Where | Credential |
|---|---|---|---|
| Visitor | Checks that the business is real | Overview, Jobs, Audit | None |
| Owner | Runs the agents and decides on their purchases | Approvals, Workforce | Owner secret |
| Customer | Pays for one job and accepts the delivery | A pay link and an accept link | Their own passkey wallet |
| Liquidity provider | Funds the pool and earns its fees | The pool contract; history on Capital pool | Their wallet, once allowlisted |
| Admin | Sets caps, allowlists and the emergency pause | The contracts directly | The 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
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.
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.
Spend
Agents buy the data and services the job needs, paying sellers over x402. Purchases within policy go through on their own.
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.
Adapt
When the owner refuses on cost, the agent looks for a cheaper source instead of routing around the decision.
Deliver
A quality check passes the draft, and the delivery’s hash is written on chain.
Accept
The customer accepts from their link. In one transaction the pool is repaid principal and fee, then the operator receives the rest.
Rate rises
The contract raises the operator’s advance rate, so the next job can borrow more.
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
- 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.
- Jobs and Activity list every job and every movement of money, each linked to its transaction.
- Capital pool shows the pool’s size, how much is lent, the advance rate over time and every deposit.
- Audit reads the safety controls live and lists what has not been proven.
For the owner
- Sign in on Settings or Approvals with the owner secret configured on this dashboard’s host. A session lasts 12 hours.
- 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.
- 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.
- 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
- 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.
- Fund the job from the same link. If the escrow is not yours, the page says so and nothing can be sent.
- 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.ioDeposit
cast send 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f \
"deposit(uint256,address)" <amount-in-micro-usdc> <your-address> \
--account <your-keystore> --rpc-url https://rpc.mainnet.arc.ioWithdraw
cast send 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f \
"withdraw(uint256,address,address)" <amount-in-micro-usdc> <your-address> <your-address> \
--account <your-keystore> --rpc-url https://rpc.mainnet.arc.ioUSDC 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.
| JobVault, the escrow | 0x67FeD7B5eaA966c4cc2738d1530f230B31B6f372 |
|---|---|
| FloatPool, the capital pool | 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f |
| AuditAnchor | 0xe8886A39158C7CC504F31789513b926704CCaB4D |
| USDC | 0x3600000000000000000000000000000000000000 |
The events behind the figures
JobCreated, JobFunded | A job and its escrowed payment |
|---|---|
AdvanceIssued | The snap: principal, fee and the rate it was issued at |
JobSettled | The fall: what the pool was repaid and what the operator kept |
AdvanceRepaid | The pool’s side of a settlement, including the reserve’s cut |
RateChanged | An operator’s new advance rate |
Deposited, Withdrawn | Liquidity 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.ioJob 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 pause | The 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. |
|---|---|
| Caps | A 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 allowlist | Only allowlisted operators can draw advances. A new grant waits 2 days; a revocation is immediate. |
| Depositor allowlist | Only allowlisted addresses can deposit into the pool. |
| Admin handover | Two steps: the current admin proposes, then the new admin accepts from its own wallet after 2 days. |
| Customer first on refunds | A 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.
| Capability | State | Detail |
|---|---|---|
| Public chain views | Working | Jobs, activity, the pool, audit and the cascade all read from the contracts. |
| Owner sign-in and approvals | Partly | Available where an owner daemon is connected. The daemon holds no signing keys yet. |
| Advances from the pool | Not yet | No treasury signer yet. It will be a Circle developer-controlled wallet, never a raw key. |
| Agent purchases over x402 | Not yet | No mainnet settlement path is configured. |
| Customer pays with a passkey wallet | Not yet | Needs a live Circle client key for this domain. |
| Settlement waterfall | Partly | One 0.50 USDC self-test job between the owner’s own wallets settled with no advance. It was not a sale. |
| Pool deposits | Not yet | The pool is paused and holds nothing. |
| Contracts with the operator allowlist | Not yet | The 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.