public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: Mike Hearn <mike@plan99•net>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Bitcoin XT
Date: Sun, 28 Dec 2014 18:04:08 +0000	[thread overview]
Message-ID: <CANEZrP2zxVgeqLZML0UUQUk8aLEZ=oY8pXdunjSq3qfakkdSHA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]

Hi there,

I hope everyone who celebrates Christmas is having a relaxing and enjoyable
break! :)

I'd like to announce Bitcoin XT <https://github.com/bitcoinxt/bitcoinxt>, 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
<https://groups.google.com/forum/#!forum/bitcoin-xt/>, and another list for
announcements <https://groups.google.com/forum/#!forum/bitcoin-xt-announce>.
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!

[-- Attachment #2: Type: text/html, Size: 2341 bytes --]

                 reply	other threads:[~2014-12-29  7:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANEZrP2zxVgeqLZML0UUQUk8aLEZ=oY8pXdunjSq3qfakkdSHA@mail.gmail.com' \
    --to=mike@plan99$(echo .)net \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox