Skip to content

specs: update sequence length and reserved bytes #1120

@rootulp

Description

@rootulp

Currently, the specs state that the sequence length is encoded as a varint and that the reserved bytes are encoded as a two byte padded varint. We recently decided to change both to big endian 4 byte unsigned integers.

Metadata

Metadata

Assignees

Labels

specsdirectly relevant to the specs

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions