Currently, there are six defined fields: - `content_type`, with a tag of `1`, whose value is the MIME type of the body. - `pointer`, with a tag of `2`, see [pointer docs](./inscriptions/pointer.md). - `parent`, with a tag of `3`, see [provenance](./inscriptions/provenance.md). - `metadata`, with a tag of `5`, see [metadata](./inscriptions/metadata.md). - `metaprotocol`, with a tag of `7`, whose value is the metaprotocol identifier. - `content_encoding`, with a tag of `9`, whose value is the encoding of the body. The beginning of the body and end of fields is indicated with an empty data push. Unrecognized tags are interpreted differently depending on whether they are even or odd, following the "it's okay to be odd" rule used by the Lightning Network. Even tags are used for fields which may affect creation, initial assignment, or transfer of an inscription. Thus, inscriptions with unrecognized even fields must be displayed as "unbound", that is, without a location. Odd tags are used for fields which do not affect creation, initial assignment,