com.publicdomainrelay.temp.market.submitEvent
Schema Diff
+1 -1
Compatibility Analysis
Backward Compatible
No changes detected.
1
1
{
2
2
"id": "com.publicdomainrelay.temp.market.submitEvent",
3
3
"defs": {
4
4
"main": {
5
5
"type": "procedure",
6
6
"input": {
7
7
"schema": {
8
8
"type": "object",
9
9
"required": [
10
10
"uri",
11
11
"cid",
12
12
"record"
13
13
],
14
14
"properties": {
15
15
"cid": {
16
16
"type": "string",
17
17
"description": "CID of the event record."
18
18
},
19
19
"uri": {
20
20
"type": "string",
21
21
"description": "AT-URI of the event record."
22
22
},
23
23
"record": {
24
24
"ref": "com.publicdomainrelay.temp.market.event",
25
25
"type": "ref",
26
26
"description": "The event record itself, including a strong reference to the receipt it pertains to."
27
27
}
28
28
}
29
29
},
30
30
"encoding": "application/json"
31
31
},
32
32
"errors": [
33
33
{
34
34
"name": "InvalidRequest"
35
35
}
36
36
],
37
37
"output": {
38
38
"schema": {
39
39
"type": "object",
40
40
"required": [
41
41
"ok"
42
42
],
43
43
"properties": {
44
44
"ok": {
45
45
"type": "boolean"
46
46
}
47
47
}
48
48
},
49
49
"encoding": "application/json"
50
50
},
51
-
"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."
51
+
"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."
52
52
}
53
53
},
54
54
"$type": "com.atproto.lexicon.schema",
55
55
"lexicon": 1
56
56
}