com.publicdomainrelay.temp.market.submitEvent

johnandersen777.bsky.social

Documentation

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 the referenced event record. The receiver additionally verifies the event's badge.blue attestations (network.attested.signature): at least one inline signature must verify against the attestation CID recomputed for the record in its authoring repository, making lifecycle claims about provider-opaque resources non-repudiable.

main 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 the referenced event record. The receiver additionally verifies the event's badge.blue attestations (network.attested.signature): at least one inline signature must verify against the attestation CID recomputed for the record in its authoring repository, making lifecycle claims about provider-opaque resources non-repudiable.

Input

Encodingapplication/json
cid string Required

CID of the event record.

uri string Required

AT-URI of the event record.

Output

Encodingapplication/json
ok boolean Required

No description available.

Errors

InvalidRequest
Try It

Requests are sent directly from your browser. Some servers may block requests due to CORS.

Base URL for XRPC calls (e.g., https://bsky.social)
Enter valid JSON for the request body
View raw schema 
{
  "type": "procedure",
  "input": {
    "schema": {
      "type": "object",
      "required": [
        "uri",
        "cid",
        "record"
      ],
      "properties": {
        "cid": {
          "type": "string",
          "description": "CID of the event record."
        },
        "uri": {
          "type": "string",
          "description": "AT-URI of the event record."
        },
        "record": {
          "ref": "com.publicdomainrelay.temp.market.event",
          "type": "ref",
          "description": "The event record itself, including a strong reference to the receipt it pertains to."
        }
      }
    },
    "encoding": "application/json"
  },
  "errors": [
    {
      "name": "InvalidRequest"
    }
  ],
  "output": {
    "schema": {
      "type": "object",
      "required": [
        "ok"
      ],
      "properties": {
        "ok": {
          "type": "boolean"
        }
      }
    },
    "encoding": "application/json"
  },
  "description": "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 the referenced event record. The receiver additionally verifies the event's badge.blue attestations (network.attested.signature): at least one inline signature must verify against the attestation CID recomputed for the record in its authoring repository, making lifecycle claims about provider-opaque resources non-repudiable."
}

Lexicon Garden

@