Lexicon Garden

com.publicdomainrelay.temp.market.submitAccept

Submit the AT-URI and CID of an accept record directly to the bidder named in the winning bid's payload, settling the contract: the bidder resolves accept->bid->rfp->vm, provisions the resource, mints a market.receipt record, and returns a strong reference to it plus its submitEvent service DID reference. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced accept record. The receiver additionally verifies badge.blue attestations (network.attested.signature) across the contract graph: the accept's inline signature, the bid's and RFP's inline signatures, and the accept payload's remote-attestation binding (receipts.* cid) before provisioning.

Repository @johnandersen777.bsky.social did:plc:5svqtrhheairglgiiyvutzik namespace authority
Details · procedure
Kindprocedure
Authoritymarket.temp.publicdomainrelay.com
Indexed
Compare Edit in builder → Fork →

Procedure

procedure · POST

Input

application/json

acceptCid

requiredstring

CID of the accept record.

acceptUri

requiredstring

AT-URI of the accept record.

Output

application/json

cid

requiredstring

CID of the newly minted receipt record.

id

requiredstring

Record key (rkey) of the newly minted receipt.

submitEvent

requiredstring

Service DID reference (did:web:HOST#compute_event) of the bidder's compute-event service, scoped to this receipt's strongRef. The requester calls com.publicdomainrelay.temp.market.submitEvent via PDS service-proxying using this value as the atproto-proxy target.

uri

requiredstring

AT-URI of the newly minted receipt record.

Errors

InvalidRequest

No description in schema.

Forbidden

No description in schema.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • com.publicdomainrelay.temp.market.submitBid

    procedure

    Submit the AT-URI and CID of a bid record directly to the RFP issuer, bypassing the firehose. Used when the RFP includes a submitBid service DID reference. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced bid record. The receiver additionally verifies the bid's badge.blue attestations (network.attested.signature): at least one inline signature must verify against the attest

  • com.publicdomainrelay.temp.market.submitRfp

    procedure

    Submit an RFP directly to a bidder whose offering record matches the RFP payload NSID. The bidder creates a bid and optionally calls submitBid back to the RFP issuer. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced RFP record. The receiver additionally verifies the RFP's badge.blue attestations (network.attested.signature): at least one inline signature must verify against

  • com.publicdomainrelay.temp.market.submitEvent

    procedure

    Submit the AT-URI and CID of an event record directly to the counterparty, bypassing the firehose. Used when the accept or receipt includes a submitEvent service DID reference — e.g. so a requester can tell a bidder to delete a VM whose workflow finished, or whose policy engine never came up, since the bidder treats the VM as a black box. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored t

  • com.publicdomainrelay.temp.market.accept

    record

    Acceptance of a bid on an RFP

  • com.publicdomainrelay.temp.market.receipt

    record

    Receipt for acceptance of a bid on an RFP