From: Tamas Blummer <tamas@bitsofproof.com>
To: Adam Back <adam@cypherspace.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT 0.11A
Date: Sun, 16 Aug 2015 20:15:26 +0200 [thread overview]
Message-ID: <0C02000B-C8D5-4206-9BFB-BE0307B4FFAF@bitsofproof.com> (raw)
In-Reply-To: <CALqxMTHoZ9EsGME76mfro9O7sd++KqJNtFRFpPJzMhAx33zxLA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1544 bytes --]
Hi Adam,
I welcomed XT for its declared focus on usability with current means.
I think there is also more room for non-consenus relevant P2P protocol flavors than a single code base can accommodate.
XT is also as Jeff just tweeted a relief valve.
It became important, that Bitcoin is able to evolve even if there are conflicting educated opinions.
If a review process serves decision making, then I’d be glad to participate.
Tamas Blummer
> On Aug 16, 2015, at 19:01, Adam Back <adam@cypherspace.org> wrote:
>
> Hi Tamas
>
> Do you find BIP 101, BIP 102, BIP 103 and the flexcap proposal
> deserving of equal consideration? Just curious because of your post.
>
> Will you be interested to participate in the BIP review process and
> perhaps attend the workshop on Bitcoin scaling announced here
> recently?
>
> Adam
>
> On 16 August 2015 at 17:07, Tamas Blummer via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> Being a bitcoin software developer an entrepreneur for years I learned that success is not a direct consequence of technology and is not inevitable.
>> BitcoinXT manifesto (https://github.com/bitcoinxt/bitcoinxt#the-xt-manifesto) should resonate with many fellow entrepreneurs.
>> I applaud Mike and Gavin for creating that choice for us.
>>
>> Tamas Blummer
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
[-- Attachment #1.2: Type: text/html, Size: 3425 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2015-08-16 18:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 17:02 [bitcoin-dev] Bitcoin XT 0.11A Mike Hearn
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 [this message]
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=0C02000B-C8D5-4206-9BFB-BE0307B4FFAF@bitsofproof.com \
--to=tamas@bitsofproof.com \
--cc=adam@cypherspace.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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