Participants
Identify the client, provider and wallet addresses associated with the agreement.
Escrow Contract Rules
The deal does not change after the money arrives.
Terms, timers and settlement paths should be visible before funding. Neither side should discover the real rules halfway through the agreement.
Defined before fundingState-based actionsRecorded deadlinesRule-based settlement
Agreement Structure
The contract defines the playing field.
A structured agreement identifies the parties, value, work, timing and settlement choices before either side becomes dependent on the other.
Payment
Define the XRP value assigned to the full agreement or individual milestones.
Deliverables
State what must be produced in language that can be reviewed against evidence.
Milestones
Divide larger projects into independently defined, reviewed and settled stages.
Deadlines
Define delivery periods and other time-dependent obligations before work begins.
Revisions
State whether revisions are included, how many apply and when that right expires.
Valid Actions
State determines what each party can do next.
Funding should not behave like review. Review should not behave like settlement. Available actions depend on the current contract and milestone state.
Before funding
Terms can be reviewed, shared or cancelled without representing an active funded agreement.
During work
The provider performs under the current milestone scope and delivery window.
During review
The client can use the actions permitted by the review rules, including approval or a valid revision request.
During revision
The provider responds within the defined correction period instead of entering an unlimited negotiation.
Settlement-ready
A completed decision path can make release or refund actions available.
Resolved
Completed, refunded, cancelled and expired agreements become terminal records.
Enforcement
Rules are useful only when they affect outcomes.
Timers have consequences
Delivery, review, revision and expiry windows can change which actions remain valid.
Extensions are bounded
Where extensions are supported, requests and decisions should be recorded rather than silently rewriting the deadline.
Evidence belongs with the agreement
Bulletin activity, submitted work and recorded actions help preserve the history behind a decision.
No universal quality oracle
Contract logic can govern timing and payment state, but it cannot make subjective work objectively excellent.
Trust Sequence
Read the complete operating model.
Rules define the agreement. State controls valid actions. Ledger activity records value movement. Risk disclosure explains the remaining limits.
Contract Rules
What governs the agreement.
Explore Contract Rules →Contract Lifecycle
How state changes over time.
Explore Contract Lifecycle →How Funds Move
Where XRP goes and why.
Explore How Funds Move →Risks
What the system cannot guarantee.
Explore Risks →Connected System
Continue into the products, architecture and evidence.
Developer Architecture
See how identity, verification, contract state and settlement fit together.
Developer Overview →Trustless Network
Use milestone agreements, workrooms and structured settlement for internet work.
Explore Trustless Network →Enforcer
Use conditional XRPL escrow with defined outcomes and expiry logic.
Explore Enforcer →Security
Review operational protections and user security responsibilities.
Review Security →Fees & Economics
Understand the 5.89% platform fee and its four equal economic buckets.
Review Fees →Proof & Transparency
Inspect the token supply, issuer, wallets, escrows and documented evidence.
Explore Transparency →Continue
Read the rules before accepting the deal.
Then follow the lifecycle to see how those rules become state transitions.
Before Funding
Product rules operate inside the broader Terms.
Read the corporate Terms, then confirm the transaction-specific rules displayed before approving payment.
Rules in practice
See how contract rules affect real users.
Connect deadlines, revisions, extensions, silence, release and refund rules to the complete Trustless Network operating workflow.
Read the Trustless contract user guide →