summaryrefslogtreecommitdiff
path: root/0f/d46c444986d13c350bb58151d3339766afebd2
blob: e10e49feffe50ea9fa43bf991602ed973d85866e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
Return-Path: <random@gmx.ch>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 15E2ECA5
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 12 Apr 2019 15:50:04 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C3E9A86E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 12 Apr 2019 15:50:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net;
	s=badeba3b8450; t=1555084198;
	bh=mPUEthuv7kmx842mbEC58Itd+iOCBKiUzfFosXXBtuY=;
	h=X-UI-Sender-Class:From:To:Cc:Subject:Date:In-Reply-To:References;
	b=iLlNC+r9l+c6EcHoJpFFsmns2DG4sJqx5uEnoXzhPZHc07RcalVcwzv/oKXt2eE2P
	wphhM+nqE6Etk7IpDIYdySm2VeCwd/0y/8x6gFi0vMSjDl1zTIbGH8pU/tgGPTllDG
	ddt4pfq2QbkLym+ywNoq1LbFCFT9YgmqO/7V6gOg=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [77.56.41.160] ([77.56.41.160]) by web-mail.gmx.net
	(3c-app-gmx-bs77.server.lan [172.19.170.225]) (via HTTP);
	Fri, 12 Apr 2019 17:49:57 +0200
MIME-Version: 1.0
Message-ID: <trinity-35c2289f-6ff5-43ee-ab71-3c0f1471284c-1555084197918@3c-app-gmx-bs77>
From: simondev1 <random@gmx.ch>
To: ZmnSCPxj@protonmail.com
Content-Type: text/html; charset=UTF-8
Date: Fri, 12 Apr 2019 17:49:57 +0200
Importance: normal
Sensitivity: Normal
In-Reply-To: <j9Yc7SPFXCH_C3wUJs5oZwwdEWQnnfcfJ_DW_DJCCH1QYCr4N9ABx3-IG9mMxKAFKHmaWE_K_XIT5hwK8aV8pGpuVYZr13sl5KQSO88vPgk=@protonmail.com>
References: <trinity-9a1b0170-a250-4c06-a8e1-0f281499c4da-1554627046019@3c-app-gmx-bs53>
	<j9Yc7SPFXCH_C3wUJs5oZwwdEWQnnfcfJ_DW_DJCCH1QYCr4N9ABx3-IG9mMxKAFKHmaWE_K_XIT5hwK8aV8pGpuVYZr13sl5KQSO88vPgk=@protonmail.com>
X-UI-Message-Type: mail
X-Priority: 3
X-Provags-ID: V03:K1:BvcUnXTgLNd+ZacqKupnEbSp3Ds4EKjctL2q7KcocyopEqFP0TLa1b0Gq2XfvaYhkjZBq
	lGo4c4xekPkTFKYL8Un+oiwp6ji/5V5TTed4sCu9hUqnsqg8Cv0aSKB/muKm1rEXoHlOOWK9ghTT
	Qr+oDfvAgd5Rn9htlkCIZRB7KwEWgZXQGbUZ6xWaOI3PYEpsbR63X/KVFCCqFVSbrDVJEmn09h/k
	nw1Gt0wmZZZW3wSUPFxhdUWqnNaQ3QCLKNqr0l9rtMLS+meSQZwRT/ybZJUNeWvlQevRQY6lPeVq
	V0=
X-UI-Out-Filterresults: notjunk:1;V03:K0:aQRO3Jbc2MA=:oRK1HQh+hsEqrrAXHpugsU
	F9eFw/jrca3hV5E7uHeuIFGFfJFoXwGGtICjdmaS5XyJOf3b0k8ye8tOgN5+whOZQUe33ddSg
	WWjXps/ZdV5ZQYc7NhuGHprHV9E+6hpRNI/SKKue1+hJMgdzSDF08NBc+n41cptFZaHmXwByp
	8/DsTmO0dhHmXD+ZbFvOTONB8JADnWt+nUdQmVqweznk/IgK1MvGVBP7/eRBvF+vOlIvVS6c3
	Cfl1VnR15Bi5/uFVVzODx9/l8QDhlxny9aOo4IFaKRKRfSH1tA3DcM21z6FeEmllkwPIHvxCw
	Ij0LpVp1FmZ36slDxBc78WuOvciTummhj6v4Iixk4V0qEv21qg/P8lvrWlni3lInUmtF3oWMS
	U/iwtm2i9+dC6cwayBjMCmWmq2kYjuMzPLYBBuIulFEMkjZkwcWeQt7w5DbYOh32RPZ2Ap2SE
	rOSefWlDIQXi1LFy4pB7n9O4OllTGMQD/Jr2Ju0CQQTQ2EiJ5qcf4aLCazDWhpppz2sRHgyzq
	SE8h2+/PhB3jBwQFLBXrQQbGXpVnCM+6/PEEi1iL88tntysAFIx/RaPKv4qKnPtQgj9mR45CK
	jSNdky5+dKYsk=
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, FREEMAIL_FROM, HTML_MESSAGE, MIME_HTML_ONLY,
	RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Sun, 14 Apr 2019 12:59:16 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] new BIP: Self balancing between excessively
 low/high fees and block size
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2019 15:50:04 -0000

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>True in case of hardfork to remove the current limit we still need a limit of lets say 8 Mbyte. To achive a valid 8MB block with this formula, the block would need to contain about 8 million btc fees. This will never happen. So probably a hard limit of 8MB would be good to avoid 1TB attacks.</div>

<div>&nbsp;</div>

<div>Regards,
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b>&nbsp;Montag, 08. April 2019 um 02:55 Uhr<br/>
<b>Von:</b>&nbsp;&quot;ZmnSCPxj&quot; &lt;ZmnSCPxj@protonmail.com&gt;<br/>
<b>An:</b>&nbsp;simondev1 &lt;random@gmx.ch&gt;, &quot;Bitcoin Protocol Discussion&quot; &lt;bitcoin-dev@lists.linuxfoundation.org&gt;<br/>
<b>Betreff:</b>&nbsp;Re: [bitcoin-dev] new BIP: Self balancing between excessively low/high fees and block size</div>

<div name="quoted-content">Good morning simondev1,<br/>
<br/>
It seems the algorithm would greatly increase validation time.<br/>
In particular, if the current limit is removed (as in hardforked proposal) then a 1Tb block can be used to attack the network, since sorting would require looking through the entire block.<br/>
Thus, validation time would still limit the practical block sizes that can be deployed with this.<br/>
<br/>
Regards,<br/>
ZmnSCPxj<br/>
<br/>
Sent with ProtonMail Secure Email.<br/>
<br/>
&#8208;&#8208;&#8208;&#8208;&#8208;&#8208;&#8208; Original Message &#8208;&#8208;&#8208;&#8208;&#8208;&#8208;&#8208;<br/>
On Sunday, April 7, 2019 4:50 PM, simondev1 via bitcoin-dev &lt;bitcoin-dev@lists.linuxfoundation.org&gt; wrote:<br/>
<br/>
&gt; Dear bitcoin developers,<br/>
&gt; &nbsp;<br/>
&gt; New BIP: <a href="https://github.com/bitcoin/bips/pull/774" target="_blank">https://github.com/bitcoin/bips/pull/774</a><br/>
&gt; &nbsp;<br/>
&gt; ==Abstract==<br/>
&gt; Logarithm of transaction fee limits block size.<br/>
&gt; &nbsp;<br/>
&gt; ==Motivation==<br/>
&gt; Keep block space small.<br/>
&gt; Waste less with spam transactions.<br/>
&gt; Auto balance Fees: Increase very low fees, Descrease very high fees.<br/>
&gt; Allow larger size when sender pays a lot.<br/>
&gt; Allow wallets to calculate/display how much average free block space there is for each fee price.<br/>
&gt; Allow senders to have more control about how the fee/priority of their transaction will behave, especially in the case of increased adoption in the future.<br/>
&gt; &nbsp;<br/>
&gt; ==Specification==<br/>
&gt; Every transaction has to fit into the following block space:<br/>
&gt; Input variable &#39;FeeInSatoshiPerByte&#39;: Must be positive or 0<br/>
&gt; type: double<br/>
&gt; unit: Satishi per byte<br/>
&gt; Output:<br/>
&gt; type: uint<br/>
&gt; unit: bytes<br/>
&gt; Formula:<br/>
&gt; floor( log10( 1.1 + FeeInSatoshiPerByte ) * 1024 * 1024 )<br/>
&gt; &nbsp;<br/>
&gt; ==Implementation==<br/>
&gt; Sort transactions by FeeInSatoshiPerByte (lowest first)<br/>
&gt; For each transaction starting from lowest FeeInSatoshiPerByte: Sum up the bytes of space used so far. Check if summed up bytes of space used so far is smaller or equal than the formula result.<br/>
&gt; If this is valid for each transaction then the blocksize is valid.<br/>
&gt; &nbsp;<br/>
&gt; ==Backward compatibility==<br/>
&gt; Soft fork: If applied AND old hardcoded block size limit is kept.<br/>
&gt; Hard fork: If applied AND old hardcoded block size limit is removed.<br/>
&gt;<br/>
&gt; Regards, simondev1<br/>
&gt;<br/>
<br/>
&nbsp;</div>
</div>
</div>
</div></div></body></html>