R5N DHT Block Types

This registry is for GNUnet DHT Block Types.

DHT Block Types types uniquely identify the different kinds of blocks that can be found in the GNUnet DHT.

This registry is used to ensure that the names and numeric values used to identify block types are uniquely defined and to allow DHT implementors to find out details about the respective semantics and human-readable syntax.

Policy

Developers working on GNUnet or packages based on GNUnet should feel free to extend this registry. Entries may be deleted if no code using them is still expected to be in production anywhere.

Updating the name of the package or subsystem is allowed provided that the code using the signature is being moved, as those fields are merely informational or used for code generation.

Entries

R5N Block Types

Name

Number

References

Comment

ANY

0

None

Identifier for any block.

FS_DBLOCK

1

None

Data block (leaf) in the CHK tree.

FS_IBLOCK

2

None

Inner block in the CHK tree.

FS_ONDEMAND

6

None

Type of a block representing a block to be encoded on demand from disk. Should never appear on the network directly.

LEGACY_HELLO

7

None

Legacy type of a block that contains a HELLO for a peer.

TEST

8

None

Block for testing.

FS_UBLOCK

9

None

Type of a block representing any type of search result (universal).

DNS

10

None

Block for storing DNS exit service advertisements.

GNS_NAMERECORD

11

None

Block for storing GNS record data.

REVOCATION

12

None

Block type for a revocation message by which a key is revoked.

DHT_HELLO

13

LSD-0004

Type of a block that contains a DHT-NG HELLO for a peer.

REGEX

22

None

Block to store a cadet regex state

REGEX_ACCEPT

23

None

Block to store a cadet regex accepting state

SET_TEST

24

None

Block for testing set/consensus. If first byte of the block is non-zero, the block is considered invalid.

CONSENSUS_ELEMENT

25

None

Block type for consensus elements. Contains either special marker elements or a nested block.

SETI_TEST

26

None

Block for testing set intersection. If first byte of the block is non-zero, the block is considered invalid.

SETU_TEST

27

None

Block for testing set union. If first byte of the block is non-zero, the block is considered invalid.