Pushed 1 commit to master
- b5babdd Add the AI usage note and the kits map. · datharnu
A client funds milestones in fUSD. A freelancer delivers the work encrypted to the client and to a 2-of-3 arbiter set. The contract releases a milestone only to the freelancer, and only with the client’s fresh ML-DSA-87 signature, a timeout, or an arbiter decision. A refund goes only to the client. The client and the freelancer are fixed when the escrow is created. No function accepts a new recipient. Being the sender of a transaction is never enough: every release, delivery, dispute, and resolution is checked with pqcVerify against the key registered for that role. Someone who steals a classical key can send transactions and still cannot release, redirect, or cancel alone. If the client does nothing through the review period, anyone can release to the freelancer. If the freelancer misses the deadline, anyone can refund the client. In a dispute, two of three arbiters can split the milestone between those two addresses only. They open the sealed deliverable in their own browsers.
EscrowFactory clones one Escrow per job: client, freelancer, arbiter set, token, milestone amounts, deadlines, and review period. Recipients never change. Each milestone moves through Funded, Delivered, then Released, Disputed, Resolved, or TimedOut. Authorisation uses haven-pq-kit: one ML-DSA signer for the client and the freelancer, and a 2-of-3 quorum for the arbiters, with separate signature domains. fUSD is funded by MsgConvertCoin into the escrow. The deliverable is encrypted in the browser. On chain is only its hash. The file key is split 2-of-3 and sealed with QoreSeal to the arbiters’ registered ML-KEM keys, so one arbiter cannot read it before a dispute is opened. Tests cover every transition and refusal, including an attacker holding each party’s classical key, plus fuzz and invariant tests that funds only ever reach the client or the freelancer. A two-stage QCAI audit is prepared with the build. The web app is the timeline: create, fund, deliver, review, release, dispute, and an arbiter console. Signing happens in the browser. The hard parts are keeping the recipient set closed, the sealed dispute evidence, and the QCAI audit.
Pushed 1 commit to master
Pushed 1 commit to master
Pushed 1 commit to master
Pushed 1 commit to master
Pushed 1 commit to master
Pushed 1 commit to master
Pushed 1 commit to master
Earned a Ship Weeks badge.
Newly verified on chain: MCP server or qore CLI, QoreScan
Pushed 1 commit to master
New project.