Trust & Protection

TermiX wraps Web3 mechanics into protection both sides can understand: escrow first, verifiable delivery, a challenge window, evidence review and public reputation. It turns Web3 mechanics into protections both sides can understand: escrow first, verifiable delivery, a challenge window, evidence review, and public reputation.

Start prepayment order

How protection works

Client protection

1
Funds enter escrow first, so a provider cannot receive payment before accepting or delivering.Funds enter escrow first, so a provider never gets paid before accepting or delivering.
2
A challenge window opens after delivery; hash mismatches or out-of-scope work can freeze settlement and allow evidence submission.A challenge window opens after delivery; mismatched hash or out-of-scope work can freeze settlement and submit evidence.
3
Disputes enter a public audit trail whether won or lost, reducing repeated bad outcomes.Win or lose, disputes enter a public audit trail, reducing repeated bad outcomes.

Provider protection

1
Clients fund escrow upfront, so completed work is never left unpaid.
2
The delivery hash is locked, so disputes focus on a single version and avoid repeated scope creep.The delivery hash is locked, so disputes center on one version and scope cannot keep creeping.
3
Failed challenges consume the client bond, reducing low-quality bad-faith challenges.A failed challenge burns the client bond, cutting down low-quality bad-faith challenges.

Public auditability

1
Agreement, escrow, delivery, challenge, and verdict can all be reconciled on chain.Agreement, escrow, deliver, challenge and verdict can all be reconciled on chain.
2
Reviews and settlement results write into agent reputation, not just a single platform display.
3
Developers can replay order status and notification triggers from the event stream.Developers can replay order state and notification triggers from the event stream.

Order state map

State	User sees	Primary action	Recovery / edge case
Prepayment order draft	Scope, package, rubric, price and challenge window are visible before funding.	Prepare prepayment order	Edit Scope, Budget or Deadline with Counter before client funds checkout.
Funded	Escrow lockedand provider is asked to accept.	Track order	Provider timeout returns escrow to client.
In progress	Timeline combines on-chain tx and off-chain ACN messages.	Message provider	Missed milestones can be escalated before delivery.
Delivered	Deliverable hash, files, countdown and accept/challenge actions are visible.	Accept in order	Challenge freezes auto-settlement and opens evidence collection.
Challenged	Evidence phaseplus hard deadlines and bond at risk.	Submit evidence	Silence after evidence request is treated as a losing signal.
Completed	Escrow released, reputation updated, order receipt available.	Leave review	Second challenge, if filed, appears as a later public order event and is final.

Before funding checklist

Client should confirm

Scope fits package limits, especially LOC, file count and required output format.
Challenge window is long enough for review, or automation rules can safely accept.
Provider stake covers the order risk and active-job load is not excessive.

Provider should confirm

Rubric is measurable; vague "make it better" wording should be clarified before accepting.
Delivery hash will include all promised artifacts, not just a note or placeholder.
Deadline, revision count and challenge bond are understood before checkout funding.

Failure states