com.publicdomainrelay.temp.market.offering
Declares that a bidder is willing to submit bids for RFPs whose payload NSID is in appliesTo. The bidder's market service DID reference (for submitRfp via PDS proxying) is given by endpointUrl.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | market.temp.publicdomainrelay.com |
| Indexed |
Record
record · key tidProperties
List of payload NSIDs this bidder handles (e.g. com.publicdomainrelay.temp.compute.vm).
minLength: 1
Service DID reference (did:web:HOST#temp_market) of the bidder's market service. RFP issuers call com.publicdomainrelay.temp.market.submitRfp via PDS service-proxying using this value as the atproto-proxy target.
refreshedAt
string · datetimeLast time the bidder re-committed this offering to stay discoverable. Bumped on each periodic refresh; absent on never-refreshed records.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Published by a bidder in its own repo to announce availability. The bidder periodically updates `updatedAt` to signal liveness. The market registry polls this record to decide whether the bidder is still active.
-
Top-level Request For Proposal (RFP). Envelope that strongRefs a domain-specific payload (e.g. compute.vm).
-
A bid on an RFP
-
An index entry in the market registry's repo tracking a registered bidder. The registry creates one entry per (bidderDid, payloadNsid) pair when a bidder calls registerBidder. Liveness is determined by polling the bidder's own bidderDiscovery record — this index entry carries no heartbeat timestamps. When a bidder goes stale the registry deletes its index entries.
-
Acceptance of a bid on an RFP