dev.cocore.compute.receipt
{
"$type": "com.atproto.lexicon.schema",
"defs": {
"generationParams": {
"description": "Sampling parameters committed to in a receipt. Integer-only because the canonical signing form forbids floats — temperature and top_p are carried as milliunits (value × 1000, e.g. temperature 0.7 -> 700).",
"properties": {
"maxTokens": {
"description": "Max output tokens requested for this job.",
"minimum": 0,
"type": "integer"
},
"seed": {
"description": "RNG seed, when the provider ran with a fixed seed (enables reproducibility claims).",
"type": "integer"
},
"temperatureMilli": {
"description": "Sampling temperature × 1000 (e.g. 0.7 -> 700). Omitted when the provider used the model default.",
"minimum": 0,
"type": "integer"
},
"topPMilli": {
"description": "Nucleus sampling top_p × 1000 (e.g. 0.95 -> 950). Omitted when the provider used the model default.",
"maximum": 1000,
"minimum": 0,
"type": "integer"
}
},
"type": "object"
},
"main": {
"key": "tid",
"record": {
"properties": {
"attestation": {
"description": "Strong-ref to a dev.cocore.compute.attestation record published by this provider. completedAt MUST fall within [attestedAt, expiresAt] of that attestation.",
"ref": "com.atproto.repo.strongRef",
"type": "ref"
},
"completedAt": {
"format": "datetime",
"type": "string"
},
"enclaveSignature": {
"description": "Secure Enclave P-256 signature (DER) over a sorted-key canonical JSON of every other field in this record. Verified against the publicKey of the strong-reffed attestation. This binding survives PDS migration: the repo-commit signature changes when keys rotate, but the enclaveSignature does not.",
"maxLength": 256,
"type": "bytes"
},
"inputCommitment": {
"description": "MUST equal job.inputCommitment.",
"maxLength": 64,
"minLength": 64,
"type": "string"
},
"job": {
"description": "Strong-ref to the requester's dev.cocore.compute.job record.",
"ref": "com.atproto.repo.strongRef",
"type": "ref"
},
"model": {
"maxLength": 256,
"type": "string"
},
"outputCipherCommitment": {
"description": "Optional SHA-256 hex over the EXACT encrypted bytes delivered to the requester (the sealed reply). Lets a requester confirm the ciphertext they received is the one the provider's enclaveSignature commits to — defends against an intermediary swapping the delivered bytes. Covered by enclaveSignature like every other field.",
"maxLength": 64,
"minLength": 64,
"type": "string"
},
"outputCipherURL": {
"description": "Optional URL where the encrypted output lives.",
"format": "uri",
"type": "string"
},
"outputCommitment": {
"description": "SHA-256 hex over the plaintext output bytes — the decrypted result the requester receives. (The earlier 'encrypted output' wording was a doc error; the provider has always committed to the plaintext, which is what a requester can verify after decrypting. Use outputCipherCommitment to commit to the encrypted bytes on the wire.)",
"maxLength": 64,
"minLength": 64,
"type": "string"
},
"params": {
"description": "Optional record of the sampling parameters the provider committed to for this job. Integer-only (canonical JSON forbids floats): temperature/top_p are carried as integer milliunits. Covered by enclaveSignature, so a requester can prove the provider claimed these settings.",
"ref": "#generationParams",
"type": "ref"
},
"price": {
"description": "MUST be <= job.priceCeiling. Currency MUST match job.priceCeiling.currency.",
"ref": "dev.cocore.compute.defs#money",
"type": "ref"
},
"proBono": {
"description": "True when the provider served this job pro bono under its `dev.cocore.compute.provider.proBono` election — free, unmetered, no exchange cut. A pro-bono receipt MUST carry `price.amount: 0` and `tokens: { in: 0, out: 0 }`: the work is explicitly not counted, so neither figure is a billing claim. An exchange settling a `proBono: true` receipt takes no fee and moves no balance (`amountCharged`, `providerPayout`, and `exchangeFee` are all 0). Covered by `enclaveSignature` like every other field, so the carve-out is part of the signed, self-verifying record rather than an off-record side channel. Absent/false ≡ a normal metered, billable receipt. Optional / additive; pre-2026-06 readers ignore it and still see a well-formed zero-price receipt.",
"type": "boolean"
},
"reasoningCommitment": {
"description": "Optional SHA-256 hex over the plaintext reasoning ('thinking') output bytes the provider produced for this job, separate from outputCommitment which covers only the answer the requester acts on. Present only when the model emitted reasoning on a distinct channel (a sibling reasoning_content field, or inline <think>...</think> tags the provider split out). Lets a requester independently verify the reasoning trace without it perturbing the answer's commitment. Covered by enclaveSignature.",
"maxLength": 64,
"minLength": 64,
"type": "string"
},
"requester": {
"description": "DID of the requester. Denormalized from the job record for indexer convenience; MUST equal the DID owning the job record.",
"format": "did",
"type": "string"
},
"sessionKeyCommitment": {
"description": "Optional SHA-256 hex over (ephemeralPubKey || sessionNonce) — the per-job ephemeral X25519 key the requester sealed the input to, bound to the request nonce. Present when the job ran under the forward-secret confidential handshake (the enclave minted a fresh ephemeral key, enclave-signed it against the requester's nonce, and the requester sealed to that key after verifying it). Lets a requester prove after the fact that its prompt was sealed to a key the measured enclave controlled for this job, not the long-lived encryptionPubKey. Covered by enclaveSignature.",
"maxLength": 64,
"minLength": 64,
"type": "string"
},
"sessionNonce": {
"description": "Optional lowercase hex of the fresh requester nonce that the ephemeral session key was bound to (the freshness challenge for this job). Pairs with sessionKeyCommitment. Covered by enclaveSignature.",
"maxLength": 64,
"minLength": 32,
"type": "string"
},
"startedAt": {
"format": "datetime",
"type": "string"
},
"tier": {
"description": "The confidentiality tier this job actually ran under. Set by the provider to `attested-confidential` only when the input was sealed to a verified, enclave-bound ephemeral session key AND served by a measured native engine under a hardware-attested posture; otherwise `best-effort`. A requester recomputes this from the receipt's attestation + sessionKeyCommitment rather than trusting the field. Optional / additive; absent equivalent to `best-effort`.",
"ref": "dev.cocore.compute.defs#tier",
"type": "ref"
},
"tokens": {
"ref": "dev.cocore.compute.defs#tokenCounts",
"type": "ref"
}
},
"required": [
"job",
"requester",
"model",
"inputCommitment",
"outputCommitment",
"tokens",
"startedAt",
"completedAt",
"price",
"attestation",
"enclaveSignature"
],
"type": "object"
},
"type": "record"
}
},
"description": "A signed receipt of a single completed compute job. Published by the provider in its own repo. Strong-refs the requester's job and the active attestation. Carries an additional Secure-Enclave-bound signature so it remains verifiable across PDS migrations.",
"id": "dev.cocore.compute.receipt",
"lexicon": 1
}
Metadata
- DID
-
did:plc:5quuhkmwe2q4k3azfsgg7kdz - CID
-
bafyreiauw7sdeytlmbfawelkbgifsyncsl64ku3u3vtxeby43i43a4q72i - Indexed At
- 2026-06-25 16:58 UTC
- AT-URI
-
at://did:plc:5quuhkmwe2q4k3azfsgg7kdz/com.atproto.lexicon.schema/dev.cocore.compute.receipt
Version History (3 versions)
Referenced Schemas (3)
Similar Lexicons
Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
dev.cocore.compute.job record
A request for computational work. Published by the requester in their own repo before the work runs, so the provider has something to commit a receipt against.
-
An exchange's signed proof of payment for a receipt. Published by the exchange in its own repo. Strong-refs both the receipt being settled and the requester's payment authorization, so the full chain is independently ve…
-
Shared type definitions for dev.cocore.compute.* records.