From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 94DA4727 for ; Fri, 31 Mar 2017 04:14:33 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-yb0-f171.google.com (mail-yb0-f171.google.com [209.85.213.171]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 08984FC for ; Fri, 31 Mar 2017 04:14:32 +0000 (UTC) Received: by mail-yb0-f171.google.com with SMTP id f204so13220294ybc.2 for ; Thu, 30 Mar 2017 21:14:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=HV/OiBlq8FKnYPWyRlvRN0JYa+YKFP9FBa9/xXR6/WA=; b=Lk0UMWkNYnyDQXG11juNo0TttOCxeE0M2k1PhuSJLfGndlF8DYnhOPKWTfaSKgGs93 dZdDoUYNFsIma+LVBoNwWy7ncFB6Rj/bx7sr/tyCCJ/jgv0HkvYg8LS9YfbTq3SUAfXy /2Zp2xP/UrahHkynZdpSrezAFEfBubdO0T5XmX+m4C4Wg+NBFHNLOQC/XDQrPp7Jnufn W4k24BPnpC7Ai2kr4y/Lsgu4JP7DYVlWrDK+OIlSt4tZMiE33zK92x1XEGFpjAqXVkMC fNzdOkTQQVujSNzcc+7E3O9si5R6RjmvKfidm7LT9e71gZzVDE9hFeUI1DxKi4ZOyKsU MgXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=HV/OiBlq8FKnYPWyRlvRN0JYa+YKFP9FBa9/xXR6/WA=; b=P11z9rmvz4j3jXbRVxf6X1FWIlfYKuwAsAKJ5H/na9LGWKMuvZzz7xcrvz2sLF3K98 9jpyFsRAGBjsJwphFBo2DCtUN+0qyY6i5SP/PqmgjkrGA6NDcoqR4xrzeh7m7ruiX+eN fgKVlVGbJee6nCo33E6i9MjGcQ8ODh6Wa7f6Nu0PoRZsiU7k/zaDtdUL6p1Mge+DJkFT I9QlH5a95TV8UBCQsoNRtES/xegS7KzUPbAZ/EO+wfjhHFDcxrG3+Af5nQrCf0FtxTUW WW7tPhveIHMO7JawfnBkwcHgIY5rx17fBvywXCYTp0/s3/kSxvJiXDK/xpOzma0ELvNM 3nbQ== X-Gm-Message-State: AFeK/H0IBcgCNBDIG1OU+rZmirlR4X4QrtjwZCpekWq1rPnCHpjZ1zU7wLTgB9r70VKRp0qkbcltfzGNz4ktDw== X-Received: by 10.37.111.136 with SMTP id k130mr591052ybc.156.1490933671940; Thu, 30 Mar 2017 21:14:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.123.135 with HTTP; Thu, 30 Mar 2017 21:14:30 -0700 (PDT) Received: by 10.37.123.135 with HTTP; Thu, 30 Mar 2017 21:14:30 -0700 (PDT) In-Reply-To: References: From: Natanael Date: Fri, 31 Mar 2017 06:14:30 +0200 Message-ID: To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a1148b846e66968054bff0b48 X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Block size adjustment idea - expedience fees + difficulty scaling proportional to block size (+ fee pool) X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2017 04:14:33 -0000 --001a1148b846e66968054bff0b48 Content-Type: text/plain; charset=UTF-8 Den 30 mars 2017 11:34 skrev "Natanael" : Block size dependent difficulty scaling. Hardfork required. Larger blocks means greater difficulty - but it doesn't scale linearly, rather a little less than linearly. That means miners can take a penalty in difficulty to claim a greater number of high fee transactions in the same amount of time (effectively increasing "block size bitrate"), increasing their profits. When such profitable fees aren't available, they have to reduce block size. In other words, the users literally pay miners to increase block size (or don't pay, which reduces it). This can be simplified if we do get a fee pool (less hardfork code, more softfork code), except that the effect will be partially reduced by the mining subsidy until it approximately reaches parity with average total fees. We don't need to alter difficulty calculation. Instead we alter the percentage of the fees that the miner gets to claim VS what he have to donate to the pool based on the size of the block he generated. Larger block = smaller percentage of fees. This is another way to pay for blocksize. The effect of this is that on average, miners that generate smaller blocks takes a share of what otherwise would be part of the mining profits of those generating larger blocks. We would need to keep pieces of the section from above on expected blocksize calculation. Because the closer you are to the expected blocksize, the more you keep. And thus we need to adjust it according to usage. --001a1148b846e66968054bff0b48 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Den 30 mars 2017 11:34 skrev "Natanael&qu= ot; <natanael.= l@gmail.com>:
Block size dependent diffi= culty scaling. Hardfork required.=C2=A0

Larger blocks means greater difficulty - but it doesn't= scale linearly, rather a little less than linearly. That means miners can = take a penalty in difficulty to claim a greater number of high fee transact= ions in the same amount of time (effectively increasing "block size bi= trate"), increasing their profits. When such profitable fees aren'= t available, they have to reduce block size.

In other words, the users literally pay miners to incr= ease block size (or don't pay, which reduces it).=C2=A0

This can be simplified if we do get a fee pool (less hardfork code, mor= e softfork code), except that the effect will be partially reduced by the m= ining subsidy until it approximately reaches parity with average total fees= .=C2=A0

We don't nee= d to alter difficulty calculation.
Instead we alter = the percentage of the fees that the miner gets to claim VS what he have to = donate to the pool based on the size of the block he generated.=C2=A0
=
Larger block =3D smaller percentage of fees. This is anot= her way to pay for blocksize. The effect of this is that on average, miners= that generate smaller blocks takes a share of what otherwise would be part= of the mining profits of those generating larger blocks.=C2=A0

We would need to keep pieces of the= section from above on expected blocksize calculation. Because the closer y= ou are to the expected blocksize, the more you keep. And thus we need to ad= just it according to usage.=C2=A0
--001a1148b846e66968054bff0b48--