# appropriated field

URL: https://blockspace.wiki/glossary/appropriated-field/

A field every transaction must have anyway, such as an input's nSequence or a transaction's nLockTime, that a protocol overloads as its message. EPOBC writes its colour tag into nSequence; CAT-21 marks a mint with nLockTime 21. The field's bytes exist regardless, so the data-types reference says BTI should attribute zero incremental bytes to the channel. Ruling B43 says such carriers are selected by the protocol writer's own rule, with any divergence named in the decoder.

Sources:

- Blockspace Holdings records
- block.space docs: data types · https://block.space/docs/datatypes

Updated: 2026-10-20