Skip to main content
Application + instance metadata.

Response

Application info.

Application + instance metadata, returned by GET /info. Mirrors what dstack-sdk client.info() returns plus a couple of Darknyx-specific fields. Used in tandem with /attestation by the SDK's verifyTeeAttestation() helper.

app_id
string
required

Hex app-id — deterministic from deployer + compose.

instance_id
string
required

Hex instance-id of this specific CVM.

app_name
string
required
compose_hash
string
required

SHA-256 of canonicalised app-compose.json. CONVENIENCE ONLY — the client's attestation check pins its EXPECTED_COMPOSE_HASH against the compose-hash read from the DCAP-VERIFIED quote's RTMR3 event log, NOT against this self-reported field (a malicious or unverified endpoint can put anything here).

boot_session_id
string
required

Fresh 32-byte process-boot session id, hex. Every canonical place and cancel intent binds this value, so requests prepared before a CVM restart cannot be replayed into the new process. The value read from /info must equal the boot session bound by the /transport-attestation manifest. It is not part of the separate signer-attestation report_data layout.

Pattern: ^[0-9a-fA-F]{64}$
transport_mode
enum<string>
required

Boot-selected transport policy. Clients pin this operational field to the independently verified transport manifest; it is not a trust root by itself.

Available options:
ra-tls,
gateway-terminated
tcb_info
object
required
device_id
string
required

TDX platform identifier of this host (PPID-derived).

tee_pubkey
string
required

Base58 Ed25519 pubkey (same as in AttestationQuote). This is the PRIMARY (shard-0) signer. Under tree-sharding the TEE derives K = num_trees signer keys (paths darknyx/ed25519-signer/v2/{0..K-1}); all K are registered in the on-chain vault_config.tee_pubkeys set via one set_tee_pubkey rotation, and each is a shard settle fee-payer. Prefer the complete set below.

tee_pubkeys
string[]
required

The FULL K-shard signer set (base58, shard order) — every key the vault accepts settle payloads from. A client reconciles this against finalized on-chain vault_config.tee_pubkeys. The quote's report_data binds SHA-256 of their raw concatenation in shard order; tee_pubkey is tee_pubkeys[0].

version
string
required

Semver tag of the darknyx-tee build (e.g. v0.4.2).