X-Git-Url: http://git.bitcoin.ninja/index.cgi?p=headersdns;a=blobdiff_plain;f=index.html;h=913f5b7bc7b66234c8a8cb6c35d92b94d9c034e2;hp=79881bae70f78f058658f6a5b8589a1d497eca9f;hb=cda7a7a3e9e19da149a62e825dc937e1a101a83e;hpb=7f17a59e065f5b39791f2e346064419e7e16050f diff --git a/index.html b/index.html index 79881ba..913f5b7 100644 --- a/index.html +++ b/index.html @@ -2,6 +2,30 @@ + + Bitcoin Headers over DNS @@ -15,27 +39,39 @@ More frightening, adding Lightning support to your wallet or system introduces new reliance on uncensorability of the P2P network, with several new avenues for attack which even Bitcoin Core likely doesn't fully protect against.

- bitcoinheaders.net exists to help provide one more, diverse, source of Bitcoin blockchain data - this time using the DNS. By fetching headers and/or neutrino filters from as many sources as possible, you can start to build reliable detection of censorship-based attacks. While this still leave mitigation of the attacks to be developed, detection is always the first step. + bitcoinheaders.net exists to help provide one more, diverse, source of Bitcoin blockchain data - this time using the DNS. By fetching headers and/or neutrino filters from as many sources as possible, you can start to build reliable detection of censorship-based attacks. While this still leaves mitigation of the attacks to be developed, detection is always the first step.

bitcoinheaders.net currently supports fetching of either full Bitcoin headers or neutrino filter headers, both with a similar format. To ensure reliable access in the face of strict DNS filters, the data is encoded in IPv6 addresses in AAAA records and DNSSec signed to prevent some basic attacks.

+

+ 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). +

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.

- The gensis block header is, thus, encoded as (note that the responses are usually not sorted):

+			The genesis block header is, thus, encoded as (note that the responses are usually not sorted):
+		

+
 0.0.bitcoinheaders.net.	604800	IN	AAAA	2001:0:1000::
 0.0.bitcoinheaders.net.	604800	IN	AAAA	2001:1000::
 0.0.bitcoinheaders.net.	604800	IN	AAAA	2001:2000::3ba:3edf
 0.0.bitcoinheaders.net.	604800	IN	AAAA	2001:3d7a:7b12:b27a:c72c:3e67:768f:617f
 0.0.bitcoinheaders.net.	604800	IN	AAAA	2001:4c81:bc38:88a5:1323:a9fb:8aa4:b1e5
-0.0.bitcoinheaders.net.	604800	IN	AAAA	2001:5e4a:29ab:5f49:ffff:1d:1dac:2b7c
-			
and the first filter header encoded as:
+0.0.bitcoinheaders.net.	604800	IN	AAAA	2001:5e4a:29ab:5f49:ffff:1d:1dac:2b7c
+

which decodes to

+

+ 0100000000000000000000000000000000000000000000000000000000000000000000003ba3edfd7a7b12b27ac72c3e67768f617fc81bc3888a51323a9fb8aa4b1e5e4a29ab5f49ffff001d1dac2b7c +

+

and the first filter header encoded as:

+
 0.0.basic.filter.bitcoinheaders.net. 604800 IN AAAA 2001:9f3:c30f:c37:fb97:7cf3:e1a3:173c
 0.0.basic.filter.bitcoinheaders.net. 604800 IN AAAA 2001:2802:139c:2020::
-0.0.basic.filter.bitcoinheaders.net. 604800 IN AAAA 2001:1631:e8ff:119a:d308:8b6f:5b2b:ced0
-			
+0.0.basic.filter.bitcoinheaders.net. 604800 IN AAAA 2001:1631:e8ff:119a:d308:8b6f:5b2b:ced0
+

which decodes to

+

+ 9f3c30f0c37fb977cf3e1a3173c631e8ff119ad3088b6f5b2bced0802139c202

You can find the scripts used to generate the zones as well as this website on GitHub.