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#
Name |
ANY |
Number |
0 |
Comment |
Identifier for any block. |
Name |
FS_DBLOCK |
Number |
1 |
Comment |
Data block (leaf) in the CHK tree. |
Name |
FS_IBLOCK |
Number |
2 |
Comment |
Inner block in the CHK tree. |
Name |
FS_ONDEMAND |
Number |
6 |
Comment |
Type of a block representing a block to be encoded on demand from disk. Should never appear on the network directly. |
Name |
LEGACY_HELLO |
Number |
7 |
Comment |
Legacy type of a block that contains a HELLO for a peer. |
Name |
TEST |
Number |
8 |
Comment |
Block for testing. |
Name |
FS_UBLOCK |
Number |
9 |
Comment |
Type of a block representing any type of search result (universal). |
Name |
DNS |
Number |
10 |
Comment |
Block for storing DNS exit service advertisements. |
Name |
GNS_NAMERECORD |
Number |
11 |
Comment |
Block for storing GNS record data. |
Name |
REVOCATION |
Number |
12 |
Comment |
Block type for a revocation message by which a key is revoked. |
Name |
DHT_HELLO |
Number |
13 |
Comment |
Type of a block that contains a DHT-NG HELLO for a peer. |
Name |
REGEX |
Number |
22 |
Comment |
Block to store a cadet regex state |
Name |
REGEX_ACCEPT |
Number |
23 |
Comment |
Block to store a cadet regex accepting state |
Name |
SET_TEST |
Number |
24 |
Comment |
Block for testing set/consensus. If first byte of the block is non-zero, the block is considered invalid. |
Name |
CONSENSUS_ELEMENT |
Number |
25 |
Comment |
Block type for consensus elements. Contains either special marker elements or a nested block. |
Name |
SETI_TEST |
Number |
26 |
Comment |
Block for testing set intersection. If first byte of the block is non-zero, the block is considered invalid. |
Name |
SETU_TEST |
Number |
27 |
Comment |
Block for testing set union. If first byte of the block is non-zero, the block is considered invalid. |