Skip to main content

Developers

Build on the settlement rail.

Post tasks, sign bids, verify proofs, watch settlement — against contracts you can read on Arbiscan.

Start here

The canonical contracts are on Arbiscan.

Software-work escrow contract

settles new software-work tasks

0x99d42927268cDC18aA31CDd97588f53dFCa12Aa0
Arbiscan ↗

Software-work verifier registry

routes new software-work tasks to their check

0xffF65E562e6c7f20982903aC85D06847e7Aa7E6A

SOFTWARE_WORK_WASM_V1 wrapper

verifies proofs for the software-work hub

0x42bCacb2709dA2fDA52a49b651A890F96a8AB438

Direct SP1 v6.1.0 verifier

software-work proofs use this verifier directly

0x082de66Fd00aBBD0d9bD24fAEe4A4a91D9E6D22F

Legacy escrow contract

settled the earlier receipts, including task 22 and the May 8 receipt

0x219f6a4206a38f05897257e40cea3b211ea5e592

Legacy verifier registry

STATS_V1 cannot settle; both repo-patch routes are inactive

0x321eb680fb52d153161a03157b1c6d97b1298350

Cost-figures check: STATS_V1 cannot settle while Succinct's SP1 v6.0.0 route is frozen, since 2026-10-09. Proof submissions revert. New software-work tasks use the direct SP1 v6.1.0 verifier.

Both hubs have a fee of 100 basis points (1%) and a minimum worker bond of 10 USDC. Route status and parameters were checked at Arbitrum One block 515499563 on 2026-10-16.

The verified Solidity on Arbiscan is the authoritative interface. Read it, then talk to us about integrating.

Integration path

One task. One lifecycle.

  1. Lock.

    Fix the task, its input commitment, and the check in the same call that locks the reward.

  2. Pick and start.

    Workers sign bids off-chain. Selection records the chosen worker; activation begins bond risk and the submit window.

  3. Check and pay.

    Submit the verifier-bound result and follow completion, or the timeout path if no valid result arrives.

Protocol invariants

The rules the integration cannot bypass.