From: Erik Aronesty <erik@q32.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: Tue, 14 Mar 2017 19:20:48 -0400 [thread overview]
Message-ID: <CAJowKgJ6=WvZbRS432E6FRMijuAwovaD9USnhp03-DcyEMH1TA@mail.gmail.com> (raw)
In-Reply-To: <CAFaEF9JFZMRFXLF0-m_=zgfScX09M07a6P4GYizWmGXOYyXEcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
- no quadratic hashing solution
- no way to prevent spamming the network to blow up block sizes
- no mention of release schedule/consensus levels, etc. should be
mentioned
- this is similar to other BIP already in place... see BIP107
On Mon, Mar 13, 2017 at 9:08 AM, ashish khandekar via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Should a BIP be submitted or are there any suggestions for the proposal ?
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 1203 bytes --]
prev parent reply other threads:[~2017-03-14 23:20 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
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 [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='CAJowKgJ6=WvZbRS432E6FRMijuAwovaD9USnhp03-DcyEMH1TA@mail.gmail.com' \
--to=erik@q32.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