Visual RFC.
ALL RFCs / RFC 8949
Read the RFC ↗
RFC 8949 / MECHANISM GUIDE

Deterministic encoding

05

A protocol can require one chosen serialization among several valid encodings.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 4.2 ↗
RFC 8949 · § 4.2EXAMPLE
3 / 3
Deterministic encodingA protocol can require one chosen serialization among several valid encodings.Deterministic encoding01Preferred shortest form of integer 1Deterministic map keys use encoded-byte orderDeterministic encoding ≠ signed or schema-valid
03
Order map entries

Apply the chosen deterministic map-key ordering before hashing or signing.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Core deterministic encoding uses preferred shortest representations.

  • Core deterministic encoding uses preferred shortest representations.
  • It disallows indefinite-length items and orders map keys by their deterministic encoded byte order.
  • Determinism does not itself provide signatures, schemas, or semantic validity.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Initial byte and arguments
  2. Strings and containers
  3. Indefinite lengths
  4. Tags and data models
  5. Deterministic encoding
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗