Update DHT registry

2 files changed, 10 insertions, 15 deletions

diff --git a/gnunet-dht-block-types/POLICY b/gnunet-dht-block-types/POLICY
deleted file mode 100644
index c87e5d0..0000000
--- a/gnunet-dht-block-types/POLICY
+++ /dev/null
@@ -1,15 +0,0 @@
-Each registry entry should contain three values: the "Number" of the
-block type, the "Name" of the block type, and a "Reference" with links
-to further information about the block type.
-
-The "Name" must be unique in the entire registry.  The value must be a
-case insensitive ASCII string and is restricted to alphanumeric
-characters.
-
-Adding records is possible after expert review, using a
-first-come-first-served policy for unique "Name" allocation.
-Experts are responsible to ensure that the chosen "Name" is
-appropriate for the block type.
-
-The current contact(s) for expert review are reachable at
-gana@gnunet.org.
diff --git a/gnunet-dht-block-types/registry.rec b/gnunet-dht-block-types/registry.rec
index 793cf1e..982b784 100644
--- a/gnunet-dht-block-types/registry.rec
+++ b/gnunet-dht-block-types/registry.rec
@@ -85,3 +85,13 @@ Number: 25
 Name: CONSENSUS_ELEMENT
 Comment: Block type for consensus elements. Contains either special marker elements or a nested block.
 References: None
+
+Number: 26
+Name: SETI_TEST
+Comment: Block for testing set intersection.  If first byte of the block is non-zero, the block is considered invalid.
+References: None
+
+Number: 27
+Name: SETU_TEST
+Comment: Block for testing set union.  If first byte of the block is non-zero, the block is considered invalid.
+References: None