Skip to content

Schemas

SealedEnvelope — pluggable cipher-bearing envelope for vault payloads

Discriminated union over `envelope` kind, used by every vault task that ships secret material across the wire (vault/upsert/0.1 → SealedSecret, vault/release/0.1 → SealedSecret in the response, vault/proxy-login/0.1 → SealedSessionBlob in the response). The cleartext shape sitting INSIDE the envelope is task-specific — VaultSecret for the secret variants, SessionBlob for the proxy-login variant — and is referenced from each task's spec. Consumers dispatch on `envelope`. An unknown envelope kind MUST be rejected (`<task>:envelope_unsupported` error code) rather than silently accepted — there is no fallback to "try parsing as DIDComm". Producers SHOULD advertise the envelope kinds they emit via `trust-task-discovery/0.1`. Forward compatibility: this union starts with three variants for the OpenVTC stack today. New variants (KERI/ACDC envelopes, a future TSP successor, hardware-attested envelopes for TEE-to-TEE transfer, etc.) land as additional `oneOf` entries — never as silent schema relaxations on an existing variant.

Schema ID
https://trusttasks.org/spec/vault/_shared/0.1/sealed-envelope
Kind
shared
Used by
3 specification versions

Trust Tasks — the registry of Trust Task specifications.

Loading the registry… If this message stays, the page's scripts could not load or run. The site needs JavaScript and access to unpkg.com.

Every specification is also on GitHub: trustoverip/dtgwg-trust-tasks-tf/specs, and the framework specification at /SPEC.md.