Note that the 0-byte in headers is meant as a version

[headersdns] / index.html

diff --git a/index.html b/index.html
index 913f5b7bc7b66234c8a8cb6c35d92b94d9c034e2..24130dcf64fc67ac418ebf93b66096a259946df9 100644 (file)
--- a/index.html
+++ b/index.html
@@ -48,7 +48,7 @@
                        Headers names are broken into sub-zones of 10,000 records, so queries should take the form of height.(height / 10000).bitcoinheaders.net (or, for basic neutrino filter headers, height.(height / 10000).basic.filter.bitcoinheaders.net).
                </p>
                <p>
-                       All headers and filter headers are encoded with an arbitrary two byte prefix (currently "2001:"), followed by a 0-indexed order nibble (as nameservers often reorder responses). Bitcoin headers are then prefixed by a single 0 byte (two 0 nibbles) and placed into the remaining 80 bytes of six IPv6 addresses. Filter headers are simply placed into three IPv6 addresses with a 17-nibble (8.5 byte) 0 suffix.
+                       All headers and filter headers are encoded with an arbitrary two byte prefix (currently "2001:"), followed by a 0-indexed order nibble (as nameservers often reorder responses). Bitcoin headers are then prefixed by a single version byte (currently version 0 - two 0 nibbles) and placed into the remaining 80 bytes of six IPv6 addresses. Filter headers are simply placed into three IPv6 addresses with a 17-nibble (8.5 byte) 0 suffix.
                </p>
                <p>
                        The genesis block header is, thus, encoded as (note that the responses are usually not sorted):