Loops HouseNear Escrow

NEAR HACKATHON
Links
Team
1 member- FAOwner
Farel
Overview
Freelancers and their clients have no neutral party: either the client pays upfront and risks nothing being delivered, or the freelancer delivers first and risks
not being paid — and platforms that "solve" this take 3-7% and hold the money themselves. We built nescrow, an escrow contract for freelance work: the client
funds the job in the same transaction that creates it, the freelancer accepts within 48 hours, work is submitted as an on-chain link, and funds release on
approval, after a 72-hour review window, or by a dispute path where an arbiter both sides named decides the split and each party withdraws their own allocation.
NEAR is not a wrapper here — it is the mechanism: the contract itself holds the escrow, so there is no custodian and no admin key that can move user funds,
transactions are cheap enough that a 1 NEAR job is still economic, named accounts make both parties human-readable on-chain, and every state change (funding,
acceptance, delivery, evidence, decision) is public and permanent. We wrote the full specification set first (FSD, state machine, contract spec, test plan),
implemented it as 31 contract methods with 113 passing tests, and deployed it live on testnet at nescrow-escrow.testnet with a React frontend that reads
everything from the chain.