From: gladoscc <admin@glados•cc>
To: Jason Livesay <ithkuil@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Quick Bitcoin/Pre-Christmas modest blocksize max increase
Date: Tue, 15 Sep 2015 01:13:08 +1000 [thread overview]
Message-ID: <CAL7-sS2HG2zbFqfzboe3LHhthwtBzZSR3pMtPikx-8fL8XD4sA@mail.gmail.com> (raw)
In-Reply-To: <CAORTeX=4pCAwnPSkLRb4w0vh116ZtTKJfq-RkeU69Fp67CwinQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
I appreciate your interest in Bitcoin, but I trust that you understand your
proposal adds nothing to the current discussion and recommend you read more
emails from this mailing list.
On 14/09/2015 11:47 am, "Jason Livesay via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> After studying the issues I believe that the situation warrants a
> short-term modest blockchain increase. Somewhere between 2mb-5mb, whatever
> the community will swallow. I recommend that happen before the winter
> shopping rush.
>
> Then, because of the fundamental technical limitations of scaling, a new
> system needs to be adopted for fast transactions. To maintain momentum
> etc., the new system ultimately settles with traditional bitcoins.
>
> In order to keep the existing brand momentum, network, and business
> investment, I believe the smoothest path forward is to build a new,
> additional system re-using the bitcoin name. I suggest this new system
> come packaged with the bitcoin core client and be referred to as
> QuickBitcoin or qbtc or something similar. As far as the public is
> concerned it could simply continue to be called bitcoin. The system will
> work on top of traditional bitcoins but have a mechanism for more/faster
> transactions. Exactly what mechanism doesn't have to be perfect, it just
> needs to be reasonably secure/useful and something that the community will
> accept.
>
> I believe this is the best way to scale bitcoin while maintaining the
> strength of its existing network, community, and branding.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 2224 bytes --]
next prev parent reply other threads:[~2015-09-14 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 1:46 Jason Livesay
2015-09-14 15:13 ` gladoscc [this message]
2015-09-16 11:23 ` phm
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=CAL7-sS2HG2zbFqfzboe3LHhthwtBzZSR3pMtPikx-8fL8XD4sA@mail.gmail.com \
--to=admin@glados$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=ithkuil@gmail$(echo .)com \
/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