02 / Tendering, on-chain

Request for Proposal

You publish what you need. Providers respond with a time frame and a proposal amount. The proposal you accept becomes the escrow — committed before any work begins.

Proposal documents of golden light converging into an escrow cube

How it flows

STEP 01

Request

You publish what you need — scope and deadline. In construction terms: the tender goes out.

STEP 02

Propose

Providers respond with a time frame and a proposal amount, recorded on-chain.

STEP 03

Commit

You accept one proposal. Its amount and time frame lock into an escrow — the provider starts work knowing the commitment is real.

STEP 04

Deliver & release

Delivered within the time frame and to your satisfaction — you release. Not delivered — you simply don't, and at expiry the escrow returns to you.

The transaction

Every RFP 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.

RFP · example transactionLocked
REQUEST#310 · scope + deadline published
PROPOSAL6-week time frame · accepted 2026-08-05

↓ becomes the escrow

ESCROW#4822 · opened from accepted proposal
ISSUERyou (the requester)
RECEIVERthe accepted provider
TERM ENDS2026-09-16 · end of proposed time frame
DELIVEREDyou release() → settles to provider
NOT DELIVEREDterm expires → returns to you

What makes it hold

Tendering, auditable

Requests, proposals, and acceptance are recorded on-chain — every bidder can verify the process was fair.

The proposal becomes the escrow

Acceptance is commitment: the proposed amount and time frame lock in before any work begins.

A deadline with teeth

Miss the time frame and there is nothing to chase — the escrow expires back to the requester on its own.

Built on the same escrow

An RFP is the escrow protocol with a tendering step in front. Same rules, same keys, same guarantees.

Next protocol

Request to Supply