- 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
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
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.
___
bitcoin-dev
Are you aware of Washington Sanchez's BIP 107? It is a proposal
similar to yours:
https://github.com/bitcoin/bips/blob/master/bip-0107.mediawiki
On Sun, Mar 12, 2017 at 4:44 PM, David Vorick via bitcoin-dev
wrote:
> What, in your appraisal, is the purpose
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.
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
BLOCKCHAIN CONGESTION – A SOLUTION AND PRE-EMPTIVE MEASURES FOR THE FUTURE
This document is an idea for helping the bitcoin block chain get
uncongested, provide enough space for transactions to get included in
blocks easily, and give the bitcoin network the power to defend itself
against any