03 / Supply, on-chain
Request to Supply
The supplier states the time frame and escrow amount up front. Your confirmation opens the escrow. Delivery earns the release — and an undelivered order simply expires back to you.
How it flows
STEP 01
List
A supplier lists what they deliver — with the time frame and escrow amount stated up front.
STEP 02
Confirm
You confirm the listing. The stated amount locks into escrow for the stated time frame — that confirmation is the order.
STEP 03
Deliver
The supplier ships knowing the escrow is committed and cannot be pulled back mid-way.
STEP 04
Release or return
You release on delivery. If nothing arrives, the escrow expires and returns to you — no refund process, no dispute queue.
The transaction
Every RTS resolves to the same on-chain object: a term-bound escrow with one key on each side. This is what both parties see for the entire term.
↓ becomes the escrow
What makes it hold
Terms stated up front
Time frame and escrow amount are part of the listing itself. Nothing is renegotiated after you commit.
Confirm to commit
Confirming a listing opens the escrow. The supplier ships against a commitment they can verify on-chain.
Release on delivery
Refund policies become unnecessary — an undelivered order expires back to the buyer by itself.
Built on the same escrow
An RTS is the escrow protocol with a supply listing in front. Same rules, same keys, same guarantees.
Next protocol
Escrow Protocol