From: David Vorick <david.vorick@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
ashish khandekar <contashk18@gmail.com>
Subject: Re: [bitcoin-dev] Solution for blockchain congestion and determination of block size by bitcoin network/protocol itself.
Date: Sun, 12 Mar 2017 10:44:20 -0400 [thread overview]
Message-ID: <CAFVRnyrzJV1fGJFnAkoHvVFvsdHGxk23SBhVwrmu=1KDvK5UUw@mail.gmail.com> (raw)
In-Reply-To: <CAFaEF9KJD7rVOALiaN6uNNzcL_u8V8uX2BLiNaTJUk98pqot=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 174 bytes --]
What, in your appraisal, is the purpose of the block size limit? I think we
will be more able to have a productive discussion around this proposal if
we clear that up first.
[-- Attachment #2: Type: text/html, Size: 196 bytes --]
next prev parent reply other threads:[~2017-03-12 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 9:51 [bitcoin-dev] Solution for blockchain congestion and determination of block size by bitcoin network/protocol itself ashish khandekar
2017-03-12 14:44 ` David Vorick [this message]
2017-03-12 14:52 ` Dionysis Zindros
2017-03-12 18:00 ` Bram Cohen
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='CAFVRnyrzJV1fGJFnAkoHvVFvsdHGxk23SBhVwrmu=1KDvK5UUw@mail.gmail.com' \
--to=david.vorick@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=contashk18@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