From: Mike Hearn <hearn@vinumeris•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin XT 0.11A
Date: Sat, 15 Aug 2015 19:02:18 +0200 [thread overview]
Message-ID: <CA+w+GKT7t5OahS-+P=QAmOyFzPnOs4J6KSo+mhSrC0YggmMupg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Hello,
As promised, we have released Bitcoin XT 0.11A which includes the bigger
blocks patch set. You can get it from
https://bitcoinxt.software/
I feel sad that it's come to this, but there is no other way. The Bitcoin
Core project has drifted so far from the principles myself and many others
feel are important, that a fork is the only way to fix things.
Forking is a natural thing in the open source community, Bitcoin is not the
first and won't be the last project to go through this. Often in forks,
people say there was insufficient communication. So to ensure everything is
crystal clear I've written a blog post and a kind of "manifesto" to
describe why this is happening and how XT plans to be different from Core
(assuming adoption, of course).
The article is here:
https://medium.com/@octskyward/why-is-bitcoin-forking-d647312d22c1
It makes no attempt to be neutral: this explains things from our point of
view.
The manifesto is on the website.
I say to all developers on this list: if you also feel that Core is no
longer serving the interests of Bitcoin users, come join us. We don't bite.
[-- Attachment #2: Type: text/html, Size: 1537 bytes --]
next reply other threads:[~2015-08-15 17:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 17:02 Mike Hearn [this message]
2015-08-15 17:57 ` s7r
2015-08-15 18:38 ` s7r
2015-08-15 19:21 ` Mike Hearn
2015-08-15 20:36 ` Milly Bitcoin
2015-08-15 20:47 ` Bryan Bishop
2015-08-15 21:10 ` Milly Bitcoin
2015-08-15 20:55 ` Micha Bailey
2015-08-15 21:32 ` Eric Lombrozo
2015-08-15 22:01 ` Ken Friece
2015-08-15 22:16 ` Eric Lombrozo
2015-08-15 22:27 ` Angel Leon
2015-08-15 22:28 ` Ken Friece
2015-08-15 22:55 ` Mark Friedenbach
2015-08-15 23:04 ` Ken Friece
2015-08-15 23:07 ` Eric Lombrozo
2015-08-15 23:30 ` Michael Naber
2015-08-15 23:40 ` Mark Friedenbach
2015-08-15 23:57 ` Ken Friece
2015-08-16 0:06 ` Milly Bitcoin
2015-08-16 13:49 ` Mike Hearn
2015-08-16 15:44 ` Anthony Towns
2015-08-16 16:07 ` Tamas Blummer
2015-08-16 16:12 ` Levin Keller
2015-08-16 17:01 ` Adam Back
2015-08-16 18:15 ` Tamas Blummer
2015-08-16 20:27 ` Eric Voskuil
2015-08-15 22:39 muyuubyou
2015-08-16 18:37 ` Andrew LeCody
2015-08-16 23:02 ` Cameron Garnham
2015-08-16 23:22 ` Andrew LeCody
2015-08-17 0:03 ` Cameron Garnham
2015-08-17 6:42 ` Peter Todd
2015-08-17 12:29 ` Andrew LeCody
2015-08-17 12:33 ` Eric Lombrozo
2015-08-19 10:09 ` Jorge Timón
2015-08-19 15:41 ` s7r
2015-08-19 22:28 ` Jorge Timón
2015-08-19 22:45 ` Adam Back
2015-08-19 23:23 ` Peter Todd
2015-08-20 10:25 ` s7r
2015-08-20 11:32 ` Milly Bitcoin
2015-08-20 11:46 ` Hector Chu
2015-08-20 12:29 ` Milly Bitcoin
2015-08-20 14:25 ` Tamas Blummer
2015-08-17 21:42 ` Matt Corallo
2015-08-16 2:08 muyuubyou
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='CA+w+GKT7t5OahS-+P=QAmOyFzPnOs4J6KSo+mhSrC0YggmMupg@mail.gmail.com' \
--to=hearn@vinumeris$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox