From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Y5VB6-0007TY-4J for bitcoin-development@lists.sourceforge.net; Mon, 29 Dec 2014 07:55:48 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.49 as permitted sender) client-ip=74.125.82.49; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f49.google.com; Received: from mail-wg0-f49.google.com ([74.125.82.49]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Y5VAq-0008SU-RJ for bitcoin-development@lists.sourceforge.net; Mon, 29 Dec 2014 07:55:48 +0000 Received: by mail-wg0-f49.google.com with SMTP id n12so18169026wgh.8 for ; Sun, 28 Dec 2014 23:55:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.235.193 with SMTP id uo1mr99840351wjc.105.1419789848159; Sun, 28 Dec 2014 10:04:08 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.9 with HTTP; Sun, 28 Dec 2014 10:04:08 -0800 (PST) Date: Sun, 28 Dec 2014 18:04:08 +0000 X-Google-Sender-Auth: L-23nxgN_9kv4hxpz6yp8nTD24w Message-ID: From: Mike Hearn To: Bitcoin Dev Content-Type: multipart/alternative; boundary=089e01419e028e2c62050b4a95b3 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 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 0.0 TIME_LIMIT_EXCEEDED Exceeded time limit / deadline X-Headers-End: 1Y5VAq-0008SU-RJ Subject: [Bitcoin-development] Bitcoin XT 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:55:48 -0000 --089e01419e028e2c62050b4a95b3 Content-Type: text/plain; charset=UTF-8 Hi there, I hope everyone who celebrates Christmas is having a relaxing and enjoyable break! :) I'd like to announce Bitcoin XT , a patch set on top of Bitcoin Core 0.10rc1 that focuses on enhancements to the peer to peer protocol. It is reproducibly built with gitian and there are binaries for Linux, OS X and Windows (code signed). It currently contains the following two features: 1. Double spend relaying, by Gavin Andresen and Tom Harding. This is useful for merchants that currently connect to thousands of nodes to spot double spends, which is wasteful of resources. 2. BIP 64 support (the getutxo message). This is useful for Lighthouse to render a more helpful GUI. By running XT you provide additional services to users of the P2P network, test the features more thoroughly and help build the case for inclusion in Bitcoin Core. There is a mailing list for discussion of patch inclusion , and another list for announcements . Because XT is a patch set the feature branches will be rebased from time to time. If you branch from them, be aware of that and plan accordingly. XT nodes advertise themselves by using the getutxo service bit (i.e. bit 2). You can find them by querying a Cartographer, which I will describe in another email. A brief note about the goals of this project. The XT project is intended to provide a friendly environment where [SPV] app developers and merchants can experiment with new features and explore new directions for the protocol, if there is demand for that. Those upgrades could then be considered for inclusion into Core at a later date. I do not expect there to be thousands of XT users any time soon, but that's OK. Because the patch set contains features that don't require everyone to opt in (e.g. changes to the tx/block formats), even just a few nodes can be useful. Thanks for reading, and have a great new year's eve! --089e01419e028e2c62050b4a95b3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi there,

I hope everyone who celebrate= s Christmas is having a relaxing and enjoyable break! :)

I'd like to announce Bitcoin XT, a patch set on top of Bitcoin Core 0.10rc1 that foc= uses on enhancements to the peer to peer protocol. It is reproducibly built= with gitian and there are binaries for Linux, OS X and Windows (code signe= d). It currently contains the following two features:
  1. Dou= ble spend relaying, by Gavin Andresen and Tom Harding. This is useful for m= erchants that currently connect to thousands of nodes to spot double spends= , which is wasteful of resources.

  2. BIP 64 support (the getut= xo message). This is useful for Lighthouse to render a more helpful GUI.
By running XT you provide additional services to users of the P= 2P network, test the features more thoroughly and help build the case for i= nclusion in Bitcoin Core.

There is a mailing list for= discussion of patch inclusion, and another list for announcements. Be= cause XT is a patch set the feature branches will be rebased from time to t= ime. If you branch from them, be aware of that and plan accordingly.
<= div>
XT nodes advertise themselves by using the getutxo servi= ce bit (i.e. bit 2). You can find them by querying a Cartographer, which I = will describe in another email.


A brief note about the goals of this project. The XT project is= intended to provide a friendly environment where [SPV] app developers and = merchants can experiment with new features and explore new directions for t= he protocol, if there is demand for that. Those upgrades could then be cons= idered for inclusion into Core at a later date. I do not expect there to be= thousands of XT users any time soon, but that's OK. Because the patch = set contains features that don't require everyone to opt in (e.g. chang= es to the tx/block formats), even just a few nodes can be useful.


Thanks for reading, and have a great new yea= r's eve!
--089e01419e028e2c62050b4a95b3--