From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z3YOI-0007BR-Ei for bitcoin-development@lists.sourceforge.net; Fri, 12 Jun 2015 23:29:38 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.174 as permitted sender) client-ip=209.85.212.174; envelope-from=pindar.wong@gmail.com; helo=mail-wi0-f174.google.com; Received: from mail-wi0-f174.google.com ([209.85.212.174]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z3YOG-0001T4-K4 for bitcoin-development@lists.sourceforge.net; Fri, 12 Jun 2015 23:29:38 +0000 Received: by wiga1 with SMTP id a1so28383944wig.0 for ; Fri, 12 Jun 2015 16:29:30 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.195.13.1 with SMTP id eu1mr30901956wjd.131.1434151770580; Fri, 12 Jun 2015 16:29:30 -0700 (PDT) Received: by 10.194.2.237 with HTTP; Fri, 12 Jun 2015 16:29:29 -0700 (PDT) In-Reply-To: References: Date: Sat, 13 Jun 2015 07:29:29 +0800 Message-ID: From: Pindar Wong To: Bryan Bishop Content-Type: multipart/alternative; boundary=047d7bd9131ad6eca005185a7ac4 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pindar.wong[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Z3YOG-0001T4-K4 Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Various block size proposals X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2015 23:29:38 -0000 --047d7bd9131ad6eca005185a7ac4 Content-Type: text/plain; charset=UTF-8 Thanks Bryan for collating these links in one great list. This is very helpful and thanks for sharing it. Feel free to fork https://github.com/EthanHeilman/BlockSizeDebate edit to add the list of proposals and create a pull request to Ethan. There's also a miningconsensus.slack.com group to have discussion w.r.t. fact/source checking, completeness (e.g. from IRC) etc. Tks. p. On Sat, Jun 13, 2015 at 3:13 AM, Bryan Bishop wrote: > Here are some proposals regarding the minimum block size questions, as > well as other related scalability issues. > > Dynamic block size limit controller (maaku) > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg07599.html > > https://www.reddit.com/r/Bitcoin/comments/35c47x/a_proposal_to_expand_the_block_size/ > > Re: dynamic block size limit controller (gmaxwell) > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg07620.html > > Various other gmaxwell-relayed ideas > > http://www.reddit.com/r/Bitcoin/comments/37pv74/gavin_andresen_moves_ahead_with_push_for_bigger/crp2735 > > Increasing the max block size using a soft-fork (Tier Nolan) > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg07927.html > > Elastic block cap with rollover penalties (Meni Rosenfield) > https://bitcointalk.org/index.php?topic=1078521 > worked example > https://bitcointalk.org/index.php?topic=1078521.msg11557115#msg11557115 > section 6.2.3 of https://cryptonote.org/whitepaper.pdf > rollover transaction fees https://bitcointalk.org/index.php?topic=80387.0 > > Variable mining effort (gmaxwell) > http://sourceforge.net/p/bitcoin/mailman/message/34100485/ > > BIP100 Soft-fork limit of 2 MB (jgarzik) > http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdf > > Transaction fee targeting > https://bitcointalk.org/index.php?topic=176684.msg9416723#msg9416723 > > Difficulty target scaling > > https://www.reddit.com/r/Bitcoin/comments/38937n/idea_make_the_difficulty_target_scale_with_block/ > > Annual 50% max block size increase > > https://www.reddit.com/r/Bitcoin/comments/351dft/what_about_gavins_2014_proposal_of_having_block/ > > Various algorithmic adjustment proposals > https://bitcointalk.org/index.php?topic=1865.0 > > https://www.reddit.com/r/Bitcoin/comments/1owbpn/is_there_a_consensus_on_the_blocksize_limit_issue/ccwd7xh > > https://www.reddit.com/r/Bitcoin/comments/35azxk/screw_the_hard_limit_lets_change_the_block_size/ > > https://www.reddit.com/r/Bitcoin/comments/359y0i/quick_question_about_the_block_size_limit_issue/ > > http://www.reddit.com/r/Bitcoin/comments/385xqj/what_if_block_size_limits_were_set_to_increase/ > http://www.age-of-bitcoin.com/dynamic-block-size-cap-scaling/ > (against) > http://garzikrants.blogspot.com/2013/02/bitcoin-block-size-thoughts.html > > Average over last 144 blocks > > http://www.reddit.com/r/Bitcoin/comments/38fmra/max_block_size_2_average_size_of_last_144_blocks/ > > Extension blocks (Adam Back) (why would he burn this idea for something so > trivial?) > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg07937.html > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg08005.html > > http://www.reddit.com/r/Bitcoin/comments/39kqzs/how_about_a_softfork_optin_blocksize_increase/ > > http://www.reddit.com/r/Bitcoin/comments/39hgzc/blockstream_cofounder_president_adam_back_phd_on/cs3tgss > > Voting by paying to an address (note: vote censorship makes this > impractical, among other reasons) > > http://www.reddit.com/r/Bitcoin/comments/3863vw/a_brandnew_idea_for_resolving_the_blocksize_debate/ > > http://www.reddit.com/r/Bitcoin/comments/1g0ywj/proposal_we_should_vote_on_the_blocksize_limit/ > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg02325.html > > Vote by paying fees > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg08164.html > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg02323.html > > Double the max block size at each block reward halving > > https://www.reddit.com/r/Bitcoin/comments/359jdc/just_double_the_max_blocksize_on_every_block/ > > Reducing the block rate instead of increasing the maximum block size > (Sergio Lerner) > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg07663.html > > https://www.reddit.com/r/Bitcoin/comments/35kpgk/sergio_lerner_on_bitcoindevelopment_reducing_the/ > > Decrease block interval > > https://www.reddit.com/r/Bitcoin/comments/2vefmp/please_eli5_besides_increasing_the_block_size_why/ > > https://www.reddit.com/r/Bitcoin/comments/35hpkt/please_remind_me_once_again_why_we_cant_decrease/ > > Increase default soft block size limit in Bitcoin Core > > http://www.reddit.com/r/Bitcoin/comments/38i6qr/why_not_increase_the_default_block_size_limit/ > https://github.com/bitcoin/bitcoin/pull/6231 > > Consider the size of the utxo set when determining max block size (note > that utxo depth cannot have consensus) > https://bitcointalk.org/index.php?topic=153401.20 > > Reduce and decrease the max block size > > https://www.reddit.com/r/Bitcoin/comments/381ygv/who_is_in_favour_of_reducing_the_blocksize_limit/ > > https://www.reddit.com/r/Bitcoin/comments/2vedt4/better_we_make_block_size_50kb_and_test/ > > Change the value of MAX_BLOCK_SIZE in Bitcoin Core > https://bitcointalk.org/index.php?topic=140233.0 > > Problems with floating block size limits (petertodd) > https://bitcointalk.org/index.php?topic=144895.0 > > Develop other ways to support high transaction volumes (gavinandresen) > https://bitcointalk.org/index.php?topic=96097.msg1059475#msg1059475 > > Simplified payment verification > https://bitcoin.org/bitcoin.pdf > > Lightning network > https://lightning.network/lightning-network-paper-DRAFT-0.5.pdf > > GHOST > https://eprint.iacr.org/2013/881.pdf > > Payment channels > https://bitcoinj.github.io/working-with-micropayments > > Tree chains > > http://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg04388.html > https://github.com/petertodd/tree-chains-paper > > fedpeg + SPV > > https://github.com/ElementsProject/elements/blob/7848ae0eed5506fb32872b6d74a12fd781aa3024/contrib/fedpeg/rotating_consensus.py > > Known missing: > - old bitcoin-development proposals > - old bitcointalk proposals > - anything unique from IRC > > On a related note, the other day I found that reading all of the -wizards > logs regarding sidechains only takes 2 hours. So... that's something. YMMV. > > - Bryan > http://heybryan.org/ > 1 512 203 0507 > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --047d7bd9131ad6eca005185a7ac4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Bryan for collating these = links in one great list. This is very helpful and thanks for sharing it.
Feel free to fork https://github.com/EthanHeilman/BlockSizeDebate
edit to add the list of proposals and create a pull request to Ethan.
=
There's also a miningconsensus.slack.com group to have discussion w.r.t. fact/sour= ce checking, completeness=C2=A0 (e.g. from IRC) etc.=C2=A0=C2=A0

Tks.

p.


<= div class=3D"gmail_quote">On Sat, Jun 13, 2015 at 3:13 AM, Bryan Bishop <k= anzure@gmail.com> wrote:
Here are some proposals regarding the minimum block siz= e questions, as well as other related scalability issues.

Dynamic block size limit controller (maaku)

Re: dynamic = block size limit controller (gmaxwell)

Various other gmaxwell= -relayed ideas

Increasi= ng the max block size using a soft-fork (Tier Nolan)

Elastic = block cap with rollover penalties (Meni Rosenfield)

Variable mining= effort (gmaxwell)

BIP100 Soft-fork li= mit of 2 MB (jgarzik)

Tran= saction fee targeting

Various algorithmic adjustment proposals
https://www.reddit.c= om/r/Bitcoin/comments/35azxk/screw_the_hard_limit_lets_change_the_block_siz= e/

Average over last 144 bl= ocks

Extension blocks (Adam Back) (= why would he burn this idea for something so trivial?)
http://www.reddit.com/r/Bitcoin/commen= ts/39hgzc/blockstream_cofounder_president_adam_back_phd_on/cs3tgss

Voting by paying to an address (note: vote censorship = makes this impractical, among other reasons)
<= a href=3D"http://www.reddit.com/r/Bitcoin/comments/1g0ywj/proposal_we_shoul= d_vote_on_the_blocksize_limit/" target=3D"_blank">http://www.reddit.com/r/B= itcoin/comments/1g0ywj/proposal_we_should_vote_on_the_blocksize_limit/<= /div>
<= br>
Vote by paying fees

Double the max block size at each bloc= k reward halving

Reducing the block rate = instead of increasing the maximum block size (Sergio Lerner)

Decrease block interval

https://github.com/bitcoin/bitcoin/pull/6231<= /div>

Consider the size of the utxo set when determining= max block size (note that utxo depth cannot have consensus)

Reduce and decrease the max block size
<= br>
Change the value of MAX_BLOCK_SIZE in Bitcoin Core

=
Problems with floating block size limits (petertodd)
<= a href=3D"https://bitcointalk.org/index.php?topic=3D144895.0" target=3D"_bl= ank">https://bitcointalk.org/index.php?topic=3D144895.0

<= /div>
Develop other ways to support high transaction volumes (gavinandr= esen)

Simplified= payment verification

=
Lightning network

GHOST=

Paymen= t channels

Tree chains

fedpeg + SPV
https://github.com/ElementsProject/elements/blob/7848ae0eed5506fb32872= b6d74a12fd781aa3024/contrib/fedpeg/rotating_consensus.py

=
Known missing:
- old bitcoin-development proposals
- old bitcointalk proposals
- anything unique from IRC

On a related note, the other day I found that reading= all of the -wizards logs regarding sidechains only takes 2 hours. So... th= at's something. YMMV.


-----------------------------------------------------------------------= -------

_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/= listinfo/bitcoin-development


--047d7bd9131ad6eca005185a7ac4--