- 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.
The genesis block header is, thus, encoded as (note that the responses are usually not sorted): @@ -74,7 +74,10 @@ 9f3c30f0c37fb977cf3e1a3173c631e8ff119ad3088b6f5b2bced0802139c202
- You can find the scripts used to generate the zones as well as this website on GitHub. + You can find the scripts used to generate the zones as well as this website via git. +
++ If you want a full block source over a protocol other than Bitcoin-P2P, a anycast-cached Bitcoin Core REST interface endpoint is available at https://bitcoin-rest.bitcoin.ninja/ for mainnet and https://testnet.bitcoin-rest.bitcoin.ninja/ for testnet3. It should go without saying that this should only be used as a backup chain source, never as the primary chain source.