From: Bram Cohen <bram@bittorrent•com>
To: ashish khandekar <contashk18@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Solution for blockchain congestion and determination of block size by bitcoin network/protocol itself.
Date: Sun, 12 Mar 2017 11:00:10 -0700 [thread overview]
Message-ID: <CA+KqGkq6K060cXfYqCekb9g2HNEeFDGL+_R2TfMF8crUHyBJSA@mail.gmail.com> (raw)
In-Reply-To: <CAFaEF9KJD7rVOALiaN6uNNzcL_u8V8uX2BLiNaTJUk98pqot=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 237 bytes --]
Shouldn't there be a FAQ about this? All the blocksize increase proposals
going back to the Bitcoin Classic have the same problems and having
repeated proposals which move the details around a bit doesn't add anything
to the discussion.
[-- Attachment #2: Type: text/html, Size: 302 bytes --]
next prev parent reply other threads:[~2017-03-12 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 9:51 ashish khandekar
2017-03-12 14:44 ` David Vorick
2017-03-12 14:52 ` Dionysis Zindros
2017-03-12 18:00 ` Bram Cohen [this message]
2017-03-13 13:08 ` ashish khandekar
2017-03-14 23:20 ` Erik Aronesty
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+KqGkq6K060cXfYqCekb9g2HNEeFDGL+_R2TfMF8crUHyBJSA@mail.gmail.com \
--to=bram@bittorrent$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=contashk18@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