Onchain work powered by Arbitrum: hire talent, fund USDC escrow, deliver milestones, and resolve disputes—with Oppy as your wallet-controlled AI assistant.
OpenWork is a decentralized work marketplace and contracting protocol built around Arbitrum. It connects hiring, USDC escrow, milestone delivery, reputation, and skill-based dispute resolution in one workflow. Oppy, our AI assistant, helps people navigate that workflow in natural language while keeping transaction approval in their wallets.
Independent professionals need confidence that agreed work will be paid. Clients need clear deliverables and control over when funds are released. Remote teams often manage the agreement in one tool, the work in another, and payment somewhere else. Disagreements then depend on fragmented evidence or a platform's internal process.
OpenWork is designed for freelancers, small teams, and organizations hiring independent talent. A concrete use case is a client hiring a developer for a series of milestones: agree on the work, fund the current milestone, submit the deliverable, and release the agreed payment through a shared contract workflow.
Find talent or bring your own: publish a job and review applications, or create a direct contract with a selected professional.
Agree on milestones: define the work and associated USDC payments, then fund the relevant milestone in smart-contract escrow.
Submit and review: record work submissions and follow the job's milestone state in the application.
Release payment: approve the completed milestone and track its payment. Supported cross-chain flows distinguish source confirmation from destination delivery.
Build trust over time: profiles, work history, reviews, skill verification, and Athena's skill-oracle dispute workflow connect payments to the people and work behind them.
Arbitrum One hosts OpenWork's canonical job and escrow logic, shared job records, profiles, and native dispute-resolution contracts. Our native Arbitrum client routes job actions to the central job contract and records. This makes Arbitrum the coordination layer for the work lifecycle.
The same-chain Arbitrum flow can create, fund, and settle a contract without a bridge. For supported cross-chain workflows, LayerZero carries application messages and Circle CCTP handles native USDC transfers. The repository also contains local-chain integrations for Optimism and XDC and governance contracts on Ethereum.
A complete work lifecycle: job discovery and direct contracts connect to escrow, submissions, payment history, profiles, and disputes.
Conversational access with user control: Oppy prepares reviewable job actions and explains transaction status. The assistant does not hold private keys or independently sign payments; the user reviews and confirms through their wallet.
Transaction-aware assistance: Oppy can inspect job state, wallet funding, and transaction evidence. It distinguishes pending or uncertain actions from confirmed actions and protects against unsafe retries.
Shared coordination across chains: users on supported networks interact with a canonical work record on Arbitrum, with separate messaging and USDC settlement paths.
Skill-based dispute handling: Athena provides an oracle-based dispute workflow alongside the job and payment system.
The stack combines React, Vite, Web3.js, Node.js, Solidity and Foundry, IPFS metadata, LayerZero messaging, and Circle CCTP. The public repository includes application and contract code, tests, deployment records, and dated execution evidence.
Recorded Arbitrum One execution: on 7 August 2026, production test job 42161-24 completed a direct-contract escrow and payment cycle. The client deposited 0.10 USDC into the job contract, and the release transaction paid the same amount to the selected applicant. This small-value internal test documents the existing product baseline before the buildathon.
Start with the demo video, then open job 42161-24 and compare its linked escrow and payout receipts. The walkthrough combines current product screens, a separate archival posting clip, and dated internal mainnet tests; it is not a new continuous transaction recording. Narration is synthetic.
Internal test job 30365-3 completed the XDC-to-Arbitrum work lifecycle on 19 July 2026: posting, application, escrow, work submission and payment release. Circle CCTP minted 0.100000 USDC into Arbitrum escrow and returned 0.099986 USDC to the XDC recipient after a 0.000014 USDC fee. This is separate from the August native-Arbitrum test and is not customer traction.
Inspect the full source/destination execution journal · View the completed cross-chain job
Oppy inspects canonical job state, funding and receipt evidence. A write becomes a review card; the browser repeats transaction checks and the user confirms through a wallet. Source confirmation, message delivery and destination payment are distinct states. Pending or uncertain actions require inspection before retrying.
OpenWork's contracts are upgradeable and include privileged configuration and owner-only emergency USDC withdrawal powers. Wallet-controlled signing does not remove administrator or upgrade risk. Independent contract review and current role/control validation remain important before broader real-money pilots. On 27 September, the application and backend regression suites passed 141 and 122 tests respectively; these are not a smart-contract audit.
Oppy architecture and evidence boundaries · Inspect canonical job-contract permissions
Following our 23 September presentation, we prepared an initial compliance issue map and a measurable pilot protocol on 27 September. This is discovery work, not legal approval or completed traction.
Scope the operating model: choose launch jurisdictions and entity; map payment roles, escrow/admin control, personal data and dispute responsibilities; take those facts to qualified review before claiming compliance.
Target a narrow first cohort: small remote teams already working with independent developers and stablecoins. Proposed discovery targets are five clients and five professionals, followed by three matched usability pairs. These are targets, not completed interviews or users.
Measure useful outcomes: first funded contract, accepted and settled milestones, total fees, elapsed time, assistance required and repeat use. Separate internal tests, external pilots and paying customers; escrow volume is not revenue.
Validate before scaling: start with native-Arbitrum usability sessions; progress to real-money pilots only after the operating, compliance and security questions are addressed.
Singapore discovery sources: MAS Payment Services Act and PDPC data-protection obligations. Singapore event participation does not determine our launch jurisdiction.
OpenWork is led by Anas, with cofounder and teammate Armand. Armand is also a cofounder of an existing freelancing platform. This experience could provide a relevant route to customer discovery, opt-in pilots and distribution. We will validate platform access, the target segment and pilot conversion before treating this as a partnership or traction. No committed user base or acquired customers are claimed from this relationship.
Open the application to explore the marketplace and work-management interface.
Meet Oppy to explore the conversational interface.
Visit the website for a product walkthrough.
OpenWork is an existing project entering the Singapore Buildathon. The implementation and dated execution evidence above describe the baseline product; event participation and confirmed buildathon additions are documented separately in Progress During Buildathon.
23 September 2026 — Presented OpenWork at the buildathon session. Feedback: focus on regulations/compliance and traction. Expanded the project page with workflow, Arbitrum architecture and existing execution evidence. 27 September 2026 — Prepared a narrated product/evidence walkthrough, judge guide, technical architecture and trust-model notes, an initial compliance issue map, and a measurable pilot protocol. Refreshed the two historical Arbitrum receipts read-only and reran existing application/backend regression suites: 141 + 122 tests passed. These checks are not a contract audit. Next validation: interview five clients and five independent professionals, observe three paired usability sessions, and measure completion, total fees, assistance and repeat use. These are proposed targets, not completed traction. Resolve the operating model and security/compliance scope before external real-money pilots. Existing baseline: application, contracts, Oppy and the July/August internal mainnet tests predate the buildathon. New materials document and explain that baseline; no new product-code delivery, paying customers, legal approval or completed pilots are claimed.
