public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: phm <moonpunter@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Quick Bitcoin/Pre-Christmas modest blocksize max increase
Date: Wed, 16 Sep 2015 06:23:52 -0500	[thread overview]
Message-ID: <55F95148.5050504@gmail.com> (raw)
In-Reply-To: <CAORTeX=4pCAwnPSkLRb4w0vh116ZtTKJfq-RkeU69Fp67CwinQ@mail.gmail.com>

Jason Livesay via bitcoin-dev wrote:
> In order to keep the existing brand momentum, network, and business
> investment, 
These are precisely the issues that the Bitcoin Development team SHOULD
NOT concern themselves with as they are not technical in nature.
> 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. 
A few members of the development team have already begun doing something
along these lines but its future does not look promising.

I do not see any indication that this Christmas will be any more or less
busy than last Christmas. Correct me if I'm wrong, but retail spending
as a whole still makes up only a small percentage of Bitcoin transactions.

phm
http://phm.link



      parent reply	other threads:[~2015-09-16 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  1:46 [bitcoin-dev] Quick Bitcoin/Pre-Christmas modest blocksize max increase Jason Livesay
2015-09-14 15:13 ` gladoscc
2015-09-16 11:23 ` phm [this message]

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=55F95148.5050504@gmail.com \
    --to=moonpunter@gmail.com \
    --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