Risk disclosure
What can go wrong
Every constraint and failure mode of milestone escrow, stated with complete clarity.
Releases are permanent and irreversible
Once a client triggers releaseFunds(pactId), the transaction immediately transfers the locked USDC into the contractor's wallet. Blockchain transactions on Arc Chain are final and cannot be clawed back, cancelled, or reversed by the Pyris team or any centralized authority.
Clients must thoroughly inspect submitted deliverables (code, design files, or reports) before authorizing release.
Deadlines, timeouts, and refunds
Every pact is initialized with a UNIX deadline. If that timestamp passes and the contractor has not called submitWork(), the smart contract allows the client to reclaim 100% of their escrowed funds via refund().
Contractors must ensure their deliverables are formally submitted onchain prior to the deadline timestamp to prevent automatic refund eligibility.
Offchain quality and subjective disputes
Smart contracts verify signatures and deadlines; they cannot autonomously judge the qualitative elegance of code, design, or written copy.
If deliverables diverge from the original agreed specifications, either party may flag the pact as Disputed. Pyris Pact provides onchain record-keeping, but parties should maintain clear written specifications and agreed revision rounds.
Smart contract execution on Arc Chain
Pyris Pact executes on PyrisPact.sol. While the contract has been stripped of complex oracle and DEX dependencies for maximal security, software bugs or network-level delays can occur.
The protocol is in open beta. Start with small amounts. See also the terms of use and documentation.