Interface ResolveResult

The x-ord-content-encoding an ord server supplied at L0/L1: that server's attestation about the envelope's tag 9, one of the four sources SPEC-GATEWAY §4 permits a consumer to read. It is the server's claim and not a verified fact, which is why it is kept apart from storedContentEncoding, whose value this resolver parsed itself.

body bytes after content-encoding handling (see decoded)

On-chain content-encoding, if the body is still encoded. Populated from an envelope parse and from nothing else, so it is only ever set on the verified paths; a transport Content-Encoding is not this (SPEC-GATEWAY §4 forbids inferring the inscription's encoding from one) and arrives as transportContentEncoding instead.

true when the resolver decoded the on-chain content-encoding

envelope-level data of the ADDRESSED inscription (not the delegate)

decoded CBOR metadata (metadata path only)

tag-9 content-encoding declared by the SERVED source's envelope, from the envelope parse (attestation-grade; transport headers are ambiguous through CDNs). Unlike contentEncoding it survives decoding; only set on verified paths, where the envelope was actually parsed.

The Content-Encoding observed on the HTTP response at L0/L1, recorded as an observation about the transport and never as a fact about the inscription. It may be an intermediary's compression, the stored tag-9 encoding, or a header a CDN wrote over plain bytes, and nothing here can tell those apart (SPEC-GATEWAY §4). Its one load-bearing use is telling a transport-decoded body apart from a real integrity mismatch (SPEC-URI §4, INTEGRITY_INDETERMINATE).

set when content was served from a delegate