From: Whit Jack <whit@whitjack.me>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP Proposal:
Date: Fri, 2 Oct 2015 12:03:05 -0700 [thread overview]
Message-ID: <A05E6A18-C93F-4878-9D94-D6A53FBA512E@whitjack.me> (raw)
/* I do not want to make anyone angry, this is sarcasm, if you are not interested, please stop here */
I would like to propose a block size algorithm based off the use of extra unneeded, unwanted data. I’m looking to see if anyone would be able to help me find potential flaws.
==Abstract==
This BIP proposes replacing the current static blocksize with a 2-part blocksize algorithm to decide on the blocksize balancing power between the miners and users. I propose an easy to implement solution for reaching consensus based on a number of factors (or variables as you programmy types like to call it).
Transaction volume and buzzword usage have been growing in a heavily correlated way for the past 6 years. If we were to base the blocksize on the usage of buzzwords, we could grow the blocksize at a reasonable rate to scale with demand.
I have outlined specifics at https://github.com/whitj00/bips/blob/master/bip-whit.mediawiki
Thanks,
Whit
reply other threads:[~2015-10-02 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=A05E6A18-C93F-4878-9D94-D6A53FBA512E@whitjack.me \
--to=whit@whitjack.me \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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