Freelance Escrow
Trustless milestone-based payments for freelance work, with built-in dispute resolution.
by abbagigo · submitted Jul 19, 2026
Community votes
0
Voting opens when this submission reaches the Top 10 stage.
Overall score
0.0/ 100
Weighted average across the 5 judging criteria.
Description
01/03
What the builder said.
Written by the team, rendered as the markdown they typed in the submission wizard.
What we built
A trustless, milestone-based payment protocol for freelance work, built on OPN Chain. Clients fund milestones directly into a smart contract, freelancers submit completed work on-chain, and funds release automatically on approval with a built-in dispute resolution path if either side disagrees.
Why
Freelance platforms today sit as mandatory intermediaries between clients and freelancers funds can be frozen, disputes are opaque, and fees eat 10-20% of every payment. None of this is technically necessary. An escrow enforced by code instead of a company removes the middleman entirely while keeping the same trust guarantees both sides need.
How it works
- Client creates a project, linking a specific freelancer's wallet
- Client funds individual milestones, each with its own amount and deadline
- Freelancer submits work on-chain once delivered (actual deliverables shared off-chain via normal channels)
- Client approves, releasing funds directly to the freelancer no processing delay, no platform fee
- Either party can raise a dispute if they disagree; a neutral arbiter resolves it with a flexible percentage split, not a binary outcome
- If a freelancer never delivers, the client can reclaim funds automatically once the deadline passes
Technical highlights
- Solidity 0.8.28, deployed via Hardhat 3 + Hardhat Ignition
- Role-based access control (client / freelancer / arbiter modifiers)
- Checks-effects-interactions pattern with explicit success checks on all transfers
- Full event log coverage for complete on-chain auditability
- React + ethers.js v6 frontend, reading all state directly from the contract with no backend or database
Roadmap
02/03
What ships next.
The builder's own next-quarter plan. Use it to gauge follow-through and ambition.
Q3 · Now
- Third-party security audit before any mainnet deployment handling real value
- Add deliverable attachments let freelancers link an IPFS hash or GitHub commit reference to each submission, tying the on-chain record to the actual work product
- Expand automated test coverage for edge cases (partial disputes, multiple concurrent milestones per project)
Q4
- Move from a single admin arbiter to a small panel or staked-juror dispute model, reducing single-point-of-trust risk
- On-chain reputation layer track completed milestone history per freelancer/client address, portable across projects
- Reusable milestone templates for common freelance work types (design sprints, dev sprints, content batches)
Beyond
- Mainnet launch once audited
- Explore integration with existing freelance marketplaces as a settlement layer, rather than a standalone platform
- Support for recurring/retainer-style freelance arrangements, not just one-off milestones
On-chain proof
03/03
1 contract on OPN Chain.
The chain itself confirmed every deployment is valid, signed by the builder's wallet, and inside the season's window.