Skip to content
gnanam1990Public

About

The self-financing AI workforce on Arc: escrowed USDC jobs, a capital pool repaid first in one settlement. Circle wallets, passkeys, x402 and CCTP proven on testnet; contracts on Arc mainnet, read-only.

Topics

Resources

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Repository files navigation

Snapfall

The self-financing AI workforce. Built on Arc.

Winner — Ignyte Stablecoins Commerce Stack Challenge.

"We gave our AI business zero dollars and one customer. Watch it finance itself."

Snapfall is an autonomous AI workforce that starts with an empty treasury. When a customer commissions a job, the business borrows working capital against the receivable it is owed (the snap), buys the data and does the work, then repays the lender out of the customer's settlement (the fall — a single-transaction waterfall). Every dollar — the advance, the expenses, the repayment, the operator's take — moves on Arc and is verifiable on the explorer without trusting the operator.

Arc Programmable Money Hackathon (Encode × Circle) · Agentic Economy + DeFi · CP3 submission Aug 9, 2026.

Live site: snapfall.lol. It reads the Arc mainnet contracts (read-only for now: see On Arc mainnet). The full product, owner views included, runs on Arc testnet at app.snapfall.lol.

On the site: how it works · support · privacy · terms. Security reports: SECURITY.md.

  • docs/CIRCLE-INTEGRATIONS.md — the five Circle products, what each one is for, and the live testnet run of each, with transactions.
  • docs/END-TO-END.md — who uses Snapfall and how, where each piece runs, one job from payment to settlement, and what works on testnet vs mainnet today.
  • docs/MAINNET.md — capital controls, the mainnet deployment, the emergency stop.
  • docs/addresses.md — every deployment, read back from chain.
  • docs/architecture.md — architecture diagram: the local/on-chain split, the settlement waterfall, and the Circle surfaces marked proven vs unproven.
  • docs/PRD.md — the product/spec definition.
  • docs/CP2-SUBMISSION.md — the CP2 progress submission.
  • docs/CIRCLE-FEEDBACK.md — Circle product feedback (Ignyte Stablecoins Commerce Stack Challenge).

On Arc mainnet

The contracts, with the capital controls in docs/MAINNET.md, were deployed on Arc mainnet (chain 5042) on 12 Nov 2026 (docs/addresses.md §9):

Contract Address
JobVault 0x67FeD7B5eaA966c4cc2738d1530f230B31B6f372
FloatPool 0xD2FaB9CD08a73B476e8DC81Afb7b57564dEef08f
AuditAnchor 0xe8886A39158C7CC504F31789513b926704CCaB4D

Deliberately tiny: every cap is 1.00 USDC (lifetime loss ceiling, per advance, per job), and deposits are allowlisted. Raising a cap and moving admin both wait out an on-chain delay. snapfall.lol/audit reads all of this live from the contracts.

Admin is the owner's wallet. On 16 Nov 2026 0x0f094eec6B569c3f33033102ad3ce33EAbFeb2fB accepted admin on JobVault (0xf668b04b…0cca, block 31,507,782) and FloatPool (0x7362bf9a…0cae, block 31,507,827). Both contracts are paused.

One self-test job has settled. Also on 16 Nov 2026, a 0.50 USDC job ran between the owner's own two wallets to prove the vault path on mainnet. It was not a customer and not a sale. It took no advance, because the pool is paused and empty, so the operator kept the whole 0.50. JobVault was unpaused for the run and paused again afterwards. Job 0x1693dd7b88579cd34d9f57675c48ad40f999285b3c1f4c53184faf679eaa9bc2, settled in 0x57cd0e9c…5033; every step is listed in docs/END-TO-END.md.

Not operating yet: no capital in the pool and no advance. This set predates the audit fixes in #126 and #127; docs/MAINNET.md retires it and redeploys from the fixed source before any liquidity is accepted. Paying from a passkey wallet is off on mainnet until Circle's mainnet (LIVE) keys and gas sponsorship are set up. The full money path below, advance included, has run on testnet, not mainnet.

Live on Arc testnet

Three contracts are deployed on Arc testnet (chain 5042002), and two jobs have run the full spine end to end — funded, advanced, delivered, settled.

Contract Address
JobVault 0x449A7308A10312b9bb0E21B62064a8080eb10bD1
FloatPool 0x4780C2E47a7eE3f9F88Bd83aace58fb32c4586bE
AuditAnchor 0x929bA0CFE0EE582949EEB0aA5c512f1EaB421519

This set was deployed on 15 Nov 2026 with the capital controls and the audit fixes. The jobs and the settlement below ran on the original 23 Jul set, whose history stays on chain (deployments/README.md).

The settlement that proves the model — 0x108a8f908b368aca286b8011d3dab34fc26c635d32df2689555ffc806ef9de4b. In that one transaction the capital pool is repaid at log index 12 and the operator is paid at log index 15. Pool first, operator second — and that ordering is the contract's control flow, not a convention or an off-chain promise: acceptDelivery calls repayAdvance before it transfers the operator's net. A lender can confirm they are made whole before the operator takes a cent by reading the transaction, trusting no one.

The Circle stack, run live on testnet

Each of these ran on Arc testnet (and Base Sepolia for CCTP) in Nov 2026, with the transactions in docs/CIRCLE-INTEGRATIONS.md:

  • The operator's treasury and gas relayer are Circle developer-controlled wallets: no raw key. The running daemon advanced working capital through the Circle treasury.
  • x402: an agent's purchase was signed by the Circle treasury and settled by the Circle relayer.
  • Customer passkey wallet (Circle Modular Wallets + Gas Station): it funded escrow and accepted delivery from the customer's own device, with gas sponsored. Acceptance ran both from /pay and from the portal's "Accept & settle from my wallet".
  • CCTP V2: the customer paid from Base Sepolia (burn → attestation → mint + fund in one operation), and the operator paid out from Arc to Base Sepolia.

The advance rate is credit, not a number

What a business can borrow against its receivables is set by its on-chain track record, and the dashboard reads it live from FloatPool.advanceRate(org):

50% → 55% (block 53290364) → 60% (block 53613272)

Each accepted job raises the rate +5% (GROWTH_BPS); each write-off lowers it −15% (PENALTY_BPS), floored at 30% and capped at 85%. The penalty is three times the reward — a rate that could only rise would not be credit. The RateChanged events carrying those ticks are on chain; the dashboard reconstructs the curve from them.

Layout

contracts/   Foundry: JobVault, FloatPool, AuditAnchor          — Anandan
daemon/      Go runtime: Brain, agents, policy, chain writer     — Gnanam
             chain indexer, reconciliation, integration          — Anandan
sidecar/     TypeScript x402 / Circle-facilitator payment rails  — Vasanth
dashboard/   Next.js dashboard (Overview, Float, approvals, …)   — Vasanth
             live activity feed, Float page, hire cards          — Anandan
docs/        PRD, ADRs, threat model, submissions
deployments/ committed chain config + the Arc EVM notes to read before a deploy
scripts/     demo seed / reset

CI

Pushes and PRs to main run the full Foundry contract suite, the Go daemon integration suite (worker-isolation and duplicate-advance gates surfaced by name), the TypeScript sidecar checks, and the dashboard typecheck / tests / build. main is kept green.

Running it locally

Requires Go 1.26+, Node 20+, and Foundry.

# contracts
cd contracts && forge test

# daemon (unit + integration; serve mode needs --deployment + signer keys, see deployments/README.md)
cd daemon && go test ./... && go run ./cmd/snapfall --help

# dashboard — reads Arc testnet by default; SNAPFALL_NETWORK=arc-mainnet for a mainnet build
cd dashboard && npm ci && npm run dev        # http://localhost:3000

Point ARC_TESTNET_RPC at a private RPC (e.g. Alchemy) for the dashboard (ARC_MAINNET_RPC for a mainnet build; see docs/MAINNET.md). The Float page reconstructs the advance-rate and fee history by scanning eth_getLogs from the deployment block (~1.45M blocks); the public Arc node's per-request range limit means that scan never completes against it and the history stays "pending." A private RPC that allows a ≥10k-block eth_getLogs range completes the scan in ~150 requests. See deployments/README.md for chain config and the Arc EVM differences worth knowing before a deploy.

Honest limits

  • The local agent activity feed is not demonstrable from a clean checkout. The daemon-side records for both settled jobs were lost, and Snapfall does not fabricate local state to stand in for them. What is verifiable is the money spine — the advance, the waterfall, and the rate curve — all on Arc and readable from the explorer. That is what the demo proves; the conversational feed is not reproducible here.
  • The USYC idle-capital sweep is a disclosed mock (MockUSYCStrategy) — Circle's permissioned USYC requires allowlisting. The mock moves real ERC-20 assets and never claims to be the real product.
  • Without a Circle client key the customer wallet is daemon-custodial, stated openly. With one, the customer self-custodies a passkey wallet and signs fund and acceptDelivery from their own device. That ran live on testnet; on mainnet it is off until a LIVE client key exists.
  • The hosted daemons are keyless, and the sidecar is not hosted. Render runs one daemon per network, reachable only on Render's private network, behind app.snapfall.lol (testnet) and the mainnet owner dashboard. They serve owner sign-in, approvals and the workforce, but hold no signing key, so they put nothing on chain. Signing and the payment sidecar have run on the operator's machine. On mainnet the signer is to come from a Circle developer-controlled wallet, never a raw key on the host (docs/END-TO-END.md, docs/HOSTING.md).
  • Scoping and quotes above the money path use a deterministic stub by default, not a live LLM, so demo runs are reproducible; the chain is authoritative for every figure that moves money. A live scoper is opt-in: set ANTHROPIC_API_KEY (model via SNAPFALL_SCOPER_MODEL, default claude-haiku-4-5) and the owner's request text is sent to Claude to produce the one-sentence scope framing. Only the scope text comes from the model — the quote and the worker kind stay deterministic, so the settlement proof above is unchanged. This is the one place local-first is qualified: with the scoper on, the owner's request text (only that — no keys, addresses, or job state) leaves the machine to Anthropic. With no key set, the deterministic stub runs and nothing leaves the machine, which is what keeps the local-first claim true by default.

Security and licence

Report vulnerabilities privately, as described in SECURITY.md.

Snapfall is released under the MIT License.

About

The self-financing AI workforce on Arc: escrowed USDC jobs, a capital pool repaid first in one settlement. Circle wallets, passkeys, x402 and CCTP proven on testnet; contracts on Arc mainnet, read-only.

Topics

Resources

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages