public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Simon Liu <simon@bitcartel.com>
To: Adam Back <adam@cypherspace.org>, Michael Naber <mickeybob@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] block-size tradeoffs & hypothetical alternatives (Re: Block size increase oppositionists: please clearly define what you need done to increase block size to a static 8MB, and help do it)
Date: Tue, 30 Jun 2015 15:55:06 -0700	[thread overview]
Message-ID: <55931E4A.80402@bitcartel.com> (raw)
In-Reply-To: <CALqxMTG1=+F8DSeRAThtTSmj4F3YhgUiCbqJ1CfBy9Z-LLZvSQ@mail.gmail.com>

My understanding is that BIP 101 has working code to raise the block
size and is ready for evaluation today.

When will Lightning and Sidechains be ready so that a fair and
controlled test can be made?

On 06/30/2015 12:54 PM, Adam Back wrote:

> People who would like to try the higher tier data-center and
> throughput by high bandwidth use route should in my opinion run that
> experiment as a layer 2 side-chain or analogous.  There are a few ways
> to do that.  And it would be appropriate to my mind that we discuss
> them here also.
> 
> An experiment like that could run in parallel with lightning, maybe it
> could be done faster, or offer different trade-offs, so could be an
> interesting and useful thing to see work on.
> 


  parent reply	other threads:[~2015-06-30 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 19:54 [bitcoin-dev] block-size tradeoffs & hypothetical alternatives (Re: Block size increase oppositionists: please clearly define what you need done to increase block size to a static 8MB, and help do it) Adam Back
2015-06-30 20:08 ` Justus Ranvier
2015-06-30 20:29   ` Milly Bitcoin
2015-06-30 22:55 ` Simon Liu [this message]
2015-06-30 22:56 ` Tom Harding

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=55931E4A.80402@bitcartel.com \
    --to=simon@bitcartel.com \
    --cc=adam@cypherspace.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=mickeybob@gmail.com \
    /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