@openvtc/trust-tasks 0.23.7 → 0.23.9

package/src/rooms/info/0.1/payload.ts

@@ -0,0 +1,572 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/rooms/info/0.1/payload.schema.json
+ */
+
+import type { AuthorityPresentation, Ext, RetentionPolicy, RoomLimits, ScopeLimits, Usage, Visibility } from "../../../_shared/components.js";
+
+
+/**
+ * A member asks a room's host what it holds about the room: its tier, its current epoch, the limits the host applies to its files, and how much of them the room and the member have used.
+ */
+export interface RoomsInfoPayload {
+  /**
+   * The room's identifier. The host verifies the presentation against credentials issued by this identifier, never against a member list of its own.
+   */
+  roomId: string;
+  /**
+   * Must confer the `read` action at this room's scope.
+   */
+  presentation: AuthorityPresentation;
+  /**
+   * Ecosystem-defined extension members per SPEC.md §4.5.1.
+   */
+  ext?: Ext;
+}
+/**
+ * Success response to rooms/info. Type https://trusttasks.org/spec/rooms/info/0.1#response.
+ */
+export interface RoomsInfoResponsePayload {
+  /**
+   * The room this describes, echoed so a response cannot be mistaken for another room's.
+   */
+  roomId: string;
+  visibility: Visibility;
+  /**
+   * Absent means `chained`, as everywhere in this family.
+   */
+  retentionPolicy?: RetentionPolicy;
+  /**
+   * The room's current epoch as the host knows it: the one a record or file must be sealed under to be accepted now.
+   */
+  epoch: number;
+  /**
+   * The limits the host applies to this room, after any override for the room and capped by the host-wide ceiling. `member` here is the room's default per-member allowance; the presenter's own, which may differ, is under `usage.member.limits`.
+   */
+  limits: RoomLimits;
+  usage: {
+    /**
+     * The room as a whole.
+     */
+    room: Usage;
+    /**
+     * The presenter's own use and allowance: charged to the subject at the root of the presented chain, so an agent sees its member's figures. Absent on a `private` room, where the host does not know which member is asking.
+     */
+    member?: {
+      usage: Usage;
+      /**
+       * The limits that apply to this member in this room: an override set for them by the host's administrators if there is one, else the room's per-member default.
+       */
+      limits: ScopeLimits;
+    };
+  };
+  ext?: Ext;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { AuthorityPresentation, Ext, RetentionPolicy, RoomLimits, ScopeLimits, Usage, Visibility };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/rooms/info/0.1" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = RoomsInfoPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/rooms/info/0.1#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = RoomsInfoResponsePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/rooms/info/0.1",
+  "title": "Rooms Info — payload",
+  "description": "A member asks a room's host what it holds about the room: its tier, its current epoch, the limits the host applies to its files, and how much of them the room and the member have used.",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "roomId",
+    "presentation"
+  ],
+  "properties": {
+    "roomId": {
+      "type": "string",
+      "description": "The room's identifier. The host verifies the presentation against credentials issued by this identifier, never against a member list of its own."
+    },
+    "presentation": {
+      "$ref": "#/$defs/AuthorityPresentation",
+      "description": "Must confer the `read` action at this room's scope."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext",
+      "description": "Ecosystem-defined extension members per SPEC.md §4.5.1."
+    }
+  },
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Rooms Info — response payload",
+      "description": "Success response to rooms/info. Type https://trusttasks.org/spec/rooms/info/0.1#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "roomId",
+        "visibility",
+        "epoch",
+        "limits",
+        "usage"
+      ],
+      "properties": {
+        "roomId": {
+          "type": "string",
+          "description": "The room this describes, echoed so a response cannot be mistaken for another room's."
+        },
+        "visibility": {
+          "$ref": "#/$defs/Visibility"
+        },
+        "retentionPolicy": {
+          "$ref": "#/$defs/RetentionPolicy",
+          "description": "Absent means `chained`, as everywhere in this family."
+        },
+        "epoch": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "The room's current epoch as the host knows it: the one a record or file must be sealed under to be accepted now."
+        },
+        "limits": {
+          "$ref": "#/$defs/RoomLimits",
+          "description": "The limits the host applies to this room, after any override for the room and capped by the host-wide ceiling. `member` here is the room's default per-member allowance; the presenter's own, which may differ, is under `usage.member.limits`."
+        },
+        "usage": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": [
+            "room"
+          ],
+          "properties": {
+            "room": {
+              "$ref": "#/$defs/Usage",
+              "description": "The room as a whole."
+            },
+            "member": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": [
+                "usage",
+                "limits"
+              ],
+              "description": "The presenter's own use and allowance: charged to the subject at the root of the presented chain, so an agent sees its member's figures. Absent on a `private` room, where the host does not know which member is asking.",
+              "properties": {
+                "usage": {
+                  "$ref": "#/$defs/Usage"
+                },
+                "limits": {
+                  "$ref": "#/$defs/ScopeLimits",
+                  "description": "The limits that apply to this member in this room: an override set for them by the host's administrators if there is one, else the room's per-member default."
+                }
+              }
+            }
+          }
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "ScopeLimits": {
+      "title": "ScopeLimits",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "Limits at one scope. Every member is optional: an absent member means the scope sets no limit of that kind, and the next wider scope's limit, or the host's ceiling, governs. All sizes are ciphertext bytes.",
+      "properties": {
+        "maxFiles": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "The number of committed blobs the scope may hold. 0 refuses every upload at this scope."
+        },
+        "maxFileBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "maximum": 1073741824,
+          "description": "The largest single blob the scope accepts. Never above 1 GiB, the transfer ceiling (BlobManifest)."
+        },
+        "maxBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "The total size of the committed and reserved blobs the scope may hold."
+        }
+      }
+    },
+    "Usage": {
+      "title": "Usage",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "files",
+        "bytes",
+        "reservedBytes"
+      ],
+      "description": "What one scope holds now. Ciphertext bytes throughout.",
+      "properties": {
+        "files": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Committed blobs that are not orphaned."
+        },
+        "bytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Their total size. A blob stops counting the moment it is orphaned (its last record dropped it or was retracted), not when the host finally deletes it, so a member who deletes a file has the room back at once."
+        },
+        "reservedBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Bytes reserved by uploads begun and not yet committed, aborted or expired. Counted against `maxBytes`, so two concurrent uploads cannot both fit under a limit only one of them fits."
+        },
+        "reservedFiles": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Uploads begun and not yet committed, aborted or expired. Counted against `maxFiles`."
+        }
+      }
+    },
+    "RoomLimits": {
+      "title": "RoomLimits",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "filesEnabled"
+      ],
+      "description": "How much a host is willing to store for one room, at the room and per member. A hosting decision, set by the host and never by anything in the room's credentials. An upload must fit every scope at once: the object against the smallest `maxFileBytes` that applies, and the member and the room with the file added.",
+      "properties": {
+        "filesEnabled": {
+          "type": "boolean",
+          "description": "False refuses every rooms/blobs/* upload for the room. Reads of blobs already stored continue."
+        },
+        "room": {
+          "$ref": "#/$defs/ScopeLimits",
+          "description": "Limits on the room as a whole."
+        },
+        "member": {
+          "$ref": "#/$defs/ScopeLimits",
+          "description": "Limits on each member's own uploads in this room, unless that member has an override. A member is the subject at the root of the authority chain they present, never the key that signed, so an agent acting on an attenuated chain spends its member's allowance. Not applied on a `private` room, where the host cannot tell members apart; the room and object limits still hold there."
+        }
+      }
+    },
+    "RetentionPolicy": {
+      "title": "RetentionPolicy",
+      "type": "string",
+      "enum": [
+        "chained",
+        "fromJoin"
+      ],
+      "description": "Whether a room keeps its history readable across a membership change, fixed at creation and immutable thereafter — like `Visibility`, and for the same reason: the rungs of an epoch key chain either exist for an epoch or they do not, and no later change of mind can seal key material that was never sealed or unseal what was already severed. `chained`: each advance produces an `EpochLink`, so every member reads the room's whole retained history however long they have been in it — what a **library** wants, at the cost of post-compromise security for record content, since a compromised current key then reaches every retained epoch. `fromJoin`: no rungs are produced, so a member reads only from the epoch their group state is at — what a **stream** wants, and what a room under a strict forward-secrecy obligation wants, at the cost that a joining member finds an empty-looking room and nobody can reread a record once their group state has moved past the epoch it was sealed under. Absent means `chained`; see the prose on why the absent case is the readable one.",
+      "$comment": "Deliberately no JSON Schema `default`. A declared default is materialised by the generated bindings — the member becomes non-optional with a serde default — so an absent value would reappear as an explicit one on re-serialisation and break round-trip idempotence for every document written before this member existed. The meaning of absence is stated in prose, where a binding cannot act on it."
+    },
+    "Visibility": {
+      "title": "Visibility",
+      "type": "string",
+      "enum": [
+        "open",
+        "attributed",
+        "private"
+      ],
+      "description": "How much of a room its host can see, fixed at creation and immutable thereafter. `open`: records are cleartext, searchable and fully audited. `attributed`: record content is sealed, and the host still learns which member acted. `private`: content is sealed and membership is presented in zero knowledge, so the host verifies that a member acted without learning which. Immutable because a downgrade cannot un-see cleartext and an upgrade would protect only what came after while presenting as though it protected everything."
+    },
+    "AuthorityPresentation": {
+      "title": "AuthorityPresentation",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "membership",
+        "authority"
+      ],
+      "description": "What a party presents to act on a room. Carries the whole authority chain: a host MUST NOT dereference an authority credential's `parent` to fetch a link it was not given. Resolving over the network would make verification depend on availability, turn every identifier into a request the host can be induced to make against an address the holder chooses, and signal credential use to whoever hosts the identifier. A host MUST bind the presenter to the chain's leaf. A chain that verifies is evidence that authority was conferred on somebody; it is not evidence that the party presenting it is that somebody. The leaf's subject MUST equal the party the host authenticated for this request — an identity the transport established or a document `proof` proved, never one named in a payload. A host that omits this check authorizes every captured presentation, and the omission is silent, because the chain still verifies.",
+      "properties": {
+        "membership": {
+          "type": "string",
+          "description": "The presenter's membership credential for this room, or — on a `private` room — a zero-knowledge presentation of it. Serialized per the governing profile."
+        },
+        "authority": {
+          "type": "array",
+          "minItems": 1,
+          "maxItems": 8,
+          "items": {
+            "type": "string"
+          },
+          "description": "The authority chain, LEAF FIRST: the first element is the credential being relied on and the last MUST be one issued by the room itself. Every link the presenter relies on is present, because the host will not fetch one. Capped at 8: verification is linear in chain length and runs on every operation, so an unbounded chain is a denial-of-service surface against the host. The known uses need 2 to 3 — a person attenuating to an agent, and that agent to a sub-agent."
+        },
+        "subjectBinding": {
+          "type": "string",
+          "description": "REQUIRED on a `private` room, where the subject identifier is withheld: a proof that the membership credential and the authority chain's leaf describe the SAME subject. Without it two parties pool credentials — one contributes membership, the other authority — and the combination verifies as a single party holding both. A host MUST refuse a private-room presentation that omits this."
+        }
+      }
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Response": {
+      "$anchor": "response",
+      "title": "Rooms Info — response payload",
+      "description": "Success response to rooms/info. Type https://trusttasks.org/spec/rooms/info/0.1#response.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "roomId",
+        "visibility",
+        "epoch",
+        "limits",
+        "usage"
+      ],
+      "properties": {
+        "roomId": {
+          "type": "string",
+          "description": "The room this describes, echoed so a response cannot be mistaken for another room's."
+        },
+        "visibility": {
+          "$ref": "#/$defs/Visibility"
+        },
+        "retentionPolicy": {
+          "$ref": "#/$defs/RetentionPolicy",
+          "description": "Absent means `chained`, as everywhere in this family."
+        },
+        "epoch": {
+          "type": "integer",
+          "minimum": 1,
+          "description": "The room's current epoch as the host knows it: the one a record or file must be sealed under to be accepted now."
+        },
+        "limits": {
+          "$ref": "#/$defs/RoomLimits",
+          "description": "The limits the host applies to this room, after any override for the room and capped by the host-wide ceiling. `member` here is the room's default per-member allowance; the presenter's own, which may differ, is under `usage.member.limits`."
+        },
+        "usage": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": [
+            "room"
+          ],
+          "properties": {
+            "room": {
+              "$ref": "#/$defs/Usage",
+              "description": "The room as a whole."
+            },
+            "member": {
+              "type": "object",
+              "additionalProperties": false,
+              "required": [
+                "usage",
+                "limits"
+              ],
+              "description": "The presenter's own use and allowance: charged to the subject at the root of the presented chain, so an agent sees its member's figures. Absent on a `private` room, where the host does not know which member is asking.",
+              "properties": {
+                "usage": {
+                  "$ref": "#/$defs/Usage"
+                },
+                "limits": {
+                  "$ref": "#/$defs/ScopeLimits",
+                  "description": "The limits that apply to this member in this room: an override set for them by the host's administrators if there is one, else the room's per-member default."
+                }
+              }
+            }
+          }
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "ScopeLimits": {
+      "title": "ScopeLimits",
+      "type": "object",
+      "additionalProperties": false,
+      "description": "Limits at one scope. Every member is optional: an absent member means the scope sets no limit of that kind, and the next wider scope's limit, or the host's ceiling, governs. All sizes are ciphertext bytes.",
+      "properties": {
+        "maxFiles": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "The number of committed blobs the scope may hold. 0 refuses every upload at this scope."
+        },
+        "maxFileBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "maximum": 1073741824,
+          "description": "The largest single blob the scope accepts. Never above 1 GiB, the transfer ceiling (BlobManifest)."
+        },
+        "maxBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "The total size of the committed and reserved blobs the scope may hold."
+        }
+      }
+    },
+    "Usage": {
+      "title": "Usage",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "files",
+        "bytes",
+        "reservedBytes"
+      ],
+      "description": "What one scope holds now. Ciphertext bytes throughout.",
+      "properties": {
+        "files": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Committed blobs that are not orphaned."
+        },
+        "bytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Their total size. A blob stops counting the moment it is orphaned (its last record dropped it or was retracted), not when the host finally deletes it, so a member who deletes a file has the room back at once."
+        },
+        "reservedBytes": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Bytes reserved by uploads begun and not yet committed, aborted or expired. Counted against `maxBytes`, so two concurrent uploads cannot both fit under a limit only one of them fits."
+        },
+        "reservedFiles": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "Uploads begun and not yet committed, aborted or expired. Counted against `maxFiles`."
+        }
+      }
+    },
+    "RoomLimits": {
+      "title": "RoomLimits",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "filesEnabled"
+      ],
+      "description": "How much a host is willing to store for one room, at the room and per member. A hosting decision, set by the host and never by anything in the room's credentials. An upload must fit every scope at once: the object against the smallest `maxFileBytes` that applies, and the member and the room with the file added.",
+      "properties": {
+        "filesEnabled": {
+          "type": "boolean",
+          "description": "False refuses every rooms/blobs/* upload for the room. Reads of blobs already stored continue."
+        },
+        "room": {
+          "$ref": "#/$defs/ScopeLimits",
+          "description": "Limits on the room as a whole."
+        },
+        "member": {
+          "$ref": "#/$defs/ScopeLimits",
+          "description": "Limits on each member's own uploads in this room, unless that member has an override. A member is the subject at the root of the authority chain they present, never the key that signed, so an agent acting on an attenuated chain spends its member's allowance. Not applied on a `private` room, where the host cannot tell members apart; the room and object limits still hold there."
+        }
+      }
+    },
+    "RetentionPolicy": {
+      "title": "RetentionPolicy",
+      "type": "string",
+      "enum": [
+        "chained",
+        "fromJoin"
+      ],
+      "description": "Whether a room keeps its history readable across a membership change, fixed at creation and immutable thereafter — like `Visibility`, and for the same reason: the rungs of an epoch key chain either exist for an epoch or they do not, and no later change of mind can seal key material that was never sealed or unseal what was already severed. `chained`: each advance produces an `EpochLink`, so every member reads the room's whole retained history however long they have been in it — what a **library** wants, at the cost of post-compromise security for record content, since a compromised current key then reaches every retained epoch. `fromJoin`: no rungs are produced, so a member reads only from the epoch their group state is at — what a **stream** wants, and what a room under a strict forward-secrecy obligation wants, at the cost that a joining member finds an empty-looking room and nobody can reread a record once their group state has moved past the epoch it was sealed under. Absent means `chained`; see the prose on why the absent case is the readable one.",
+      "$comment": "Deliberately no JSON Schema `default`. A declared default is materialised by the generated bindings — the member becomes non-optional with a serde default — so an absent value would reappear as an explicit one on re-serialisation and break round-trip idempotence for every document written before this member existed. The meaning of absence is stated in prose, where a binding cannot act on it."
+    },
+    "Visibility": {
+      "title": "Visibility",
+      "type": "string",
+      "enum": [
+        "open",
+        "attributed",
+        "private"
+      ],
+      "description": "How much of a room its host can see, fixed at creation and immutable thereafter. `open`: records are cleartext, searchable and fully audited. `attributed`: record content is sealed, and the host still learns which member acted. `private`: content is sealed and membership is presented in zero knowledge, so the host verifies that a member acted without learning which. Immutable because a downgrade cannot un-see cleartext and an upgrade would protect only what came after while presenting as though it protected everything."
+    },
+    "AuthorityPresentation": {
+      "title": "AuthorityPresentation",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "membership",
+        "authority"
+      ],
+      "description": "What a party presents to act on a room. Carries the whole authority chain: a host MUST NOT dereference an authority credential's `parent` to fetch a link it was not given. Resolving over the network would make verification depend on availability, turn every identifier into a request the host can be induced to make against an address the holder chooses, and signal credential use to whoever hosts the identifier. A host MUST bind the presenter to the chain's leaf. A chain that verifies is evidence that authority was conferred on somebody; it is not evidence that the party presenting it is that somebody. The leaf's subject MUST equal the party the host authenticated for this request — an identity the transport established or a document `proof` proved, never one named in a payload. A host that omits this check authorizes every captured presentation, and the omission is silent, because the chain still verifies.",
+      "properties": {
+        "membership": {
+          "type": "string",
+          "description": "The presenter's membership credential for this room, or — on a `private` room — a zero-knowledge presentation of it. Serialized per the governing profile."
+        },
+        "authority": {
+          "type": "array",
+          "minItems": 1,
+          "maxItems": 8,
+          "items": {
+            "type": "string"
+          },
+          "description": "The authority chain, LEAF FIRST: the first element is the credential being relied on and the last MUST be one issued by the room itself. Every link the presenter relies on is present, because the host will not fetch one. Capped at 8: verification is linear in chain length and runs on every operation, so an unbounded chain is a denial-of-service surface against the host. The known uses need 2 to 3 — a person attenuating to an agent, and that agent to a sub-agent."
+        },
+        "subjectBinding": {
+          "type": "string",
+          "description": "REQUIRED on a `private` room, where the subject identifier is withheld: a proof that the membership credential and the authority chain's leaf describe the SAME subject. Without it two parties pool credentials — one contributes membership, the other authority — and the combination verifies as a single party holding both. A host MUST refuse a private-room presentation that omits this."
+        }
+      }
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: false,
+  isRecipientRequired: true,
+  isIssuedAtRequired: false,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: false,
+  isRecipientRequired: true,
+  isIssuedAtRequired: false,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;