From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Y5Un1-0004Ia-0g for bitcoin-development@lists.sourceforge.net; Mon, 29 Dec 2014 07:30:55 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.50 as permitted sender) client-ip=74.125.82.50; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f50.google.com; Received: from mail-wg0-f50.google.com ([74.125.82.50]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Y5Umw-0003CU-9G for bitcoin-development@lists.sourceforge.net; Mon, 29 Dec 2014 07:30:54 +0000 Received: by mail-wg0-f50.google.com with SMTP id a1so18410101wgh.9 for ; Sun, 28 Dec 2014 23:30:44 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.82.98 with SMTP id h2mr3982906wiy.7.1419791129297; Sun, 28 Dec 2014 10:25:29 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.9 with HTTP; Sun, 28 Dec 2014 10:25:29 -0800 (PST) Date: Sun, 28 Dec 2014 18:25:29 +0000 X-Google-Sender-Auth: 4jwgr-WMWDSQ9mQpRBoLHhJ8Y8Y Message-ID: From: Mike Hearn To: Bitcoin Dev Content-Type: multipart/alternative; boundary=f46d044283eceacc1c050b4ae114 X-Spam-Score: 0.3 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) 0.8 DATE_IN_PAST_12_24 Date: is 12 to 24 hours before Received: date -0.0 SPF_PASS SPF: sender matches SPF record 0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Y5Umw-0003CU-9G Subject: [Bitcoin-development] Cartographer X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2014 07:30:55 -0000 --f46d044283eceacc1c050b4ae114 Content-Type: text/plain; charset=UTF-8 Hi there! Lately we have been bumping up against the limitations of DNS as a protocol for learning about the p2p network. As a proposal for how to address this, I have written a new network crawler and seed: https://github.com/mikehearn/httpseed It implements a standard DNS seed with a minimal embedded DNS server (you can find one running at dnsseed.vinumeris.com) and also has the following extra features: - Can serve seed data using gzipped, timestamped digitally signed protocol buffers over HTTP. This fixes authentication, auditability, malware false positives and extensibility. The signature uses secp256k1. SSL is *not* used, to simplify deployment and to allow ISPs to cache the results transparently when a future version sets cache control headers. - Can additionally serve data in JSON, XML and HTML (examples for json xml html ) for ease of use with other tools, like web browsers. - Results can be restricted using query parameters, e.g. for a service flags bit mask. Cartographer tests nodes that set service bit 2 to see if they really support BIP 64, and this requirement can also be specified as an argument to the query. - Crawl speed can be specified in terms of successful connects per second, rather than the number-of-threads approach used by other crawlers. - Can export statistics and controls using JMX, so you can reconfigure it at runtime and view charts of things like connects/sec or CPU usage using any JMX console, like Mission Control. - A client for it is in bitcoinj master branch. To provide all these features Cartographer relies heavily on libraries and is written in a concise new language called Kotlin , so it fits in about 650 lines of code. Kotlin is easy to learn for anyone who knows Scala or Java, so it should be straightforward to hack on and there is no chance of any buffer/heap exploits in the DNS, HTTP or Bitcoin protocol stacks. In the new year I will probably write a BIP describing the protocol. For now you can see the definition here or just read the textual forms from the links above. It's pretty self explanatory. I hope that in future other DNS seeds will start supporting this protocol too, as it has many advantages. Future versions might include data like how long the peer has been around, node keys if we add auth/encrypt support to the p2p protocol and so on. --f46d044283eceacc1c050b4ae114 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi there!

Lately we have been bumping u= p against the limitations of DNS as a protocol for learning about the p2p n= etwork. As a proposal for how to address this, I have written a new network= crawler and seed:

=
It implements a standard DNS seed with a minimal embedded DN= S server (you can find one running at dnsseed.vinumeris.com) and also has the following extra features:

  • Can serve seed data using gzipped, timestamped= digitally signed protocol buffers over HTTP. This fixes authentication, au= ditability, malware false positives and extensibility. The signature uses s= ecp256k1. SSL is not=C2=A0used, to simplify deployment and to allow = ISPs to cache the results transparently when a future version sets cache co= ntrol headers.
  • Can additionally serve data in JSON, XML and HTML (e= xamples for json xml html)=C2=A0for ease of use with other tools, l= ike web browsers.
  • Results can be restricted using query parameters,= e.g. for a service flags bit mask. Cartographer tests nodes that set servi= ce bit 2 to see if they really support BIP 64, and this requirement can als= o be specified as an argument to the query.
  • Crawl speed can be specified in terms of successful= connects per second, rather than the number-of-threads approach used by ot= her crawlers.
  • Can export statistics and controls using J= MX, so you can reconfigure it at runtime and view charts of things like con= nects/sec or CPU usage using any JMX console, like Mission Control.
    • A client for it is in bitcoinj master branch.
To provide all thes= e features Cartographer relies heavily on libraries and is written in a con= cise new language called Kotlin, so = it fits in about 650 lines of code. Kotlin is easy to learn for anyone who = knows Scala or Java, so it should be straightforward to hack on and there i= s no chance of any buffer/heap exploits in the DNS, HTTP or Bitcoin protoco= l stacks.

In the new year I wi= ll probably write a BIP describing the protocol. For now you can see the de= finition here or just read the textual forms from the links= above. It's pretty self explanatory. I hope that in future other DNS s= eeds will start supporting this protocol too, as it has many advantages.

Future versions might include data like how long the= peer has been around, node keys if we add auth/encrypt support to the p2p = protocol and so on.
--f46d044283eceacc1c050b4ae114--