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
|
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 3EECCCA0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 12 Apr 2019 15:45:32 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2F34386E
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 12 Apr 2019 15:45:30 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net;
s=badeba3b8450; t=1555083925;
bh=3/bU/tOXAwcLuOXfEm1twA9CtkaTgzdH7zh7v9TYdaU=;
h=X-UI-Sender-Class:From:To:Cc:Subject:Date:In-Reply-To:References;
b=ZjvCVOgrPGrjphK80KZbWpV4lLgpiTeVPKcN2uQwpiiC0G4ZV6CqrSWk6Cj8UHLmv
T4vShNki1K6uzd5V05+cTsHl6Mxf/bwAqRR2s84xm4iD3CsCCpn5cMpbGDdNozJVMd
KBFkYalNaf3+zvGjCt/UVlC1VskDhiCaDDelEeDQ=
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:45:25 +0200
MIME-Version: 1.0
Message-ID: <trinity-20a3d4d6-ff4a-488f-9288-d10c0388887a-1555083925577@3c-app-gmx-bs77>
From: simondev1 <random@gmx.ch>
To: "Bernd Jendrissek" <bitcoin@bpj-code.co.za>
Content-Type: text/html; charset=UTF-8
Date: Fri, 12 Apr 2019 17:45:25 +0200
Importance: normal
Sensitivity: Normal
In-Reply-To: <CAF7PVPrXg2nefBkPH6E1Qz8hvL8JVSn-mCRCK60TtY1NjA-z3w@mail.gmail.com>
References: <trinity-9a1b0170-a250-4c06-a8e1-0f281499c4da-1554627046019@3c-app-gmx-bs53>
<CAF7PVPrXg2nefBkPH6E1Qz8hvL8JVSn-mCRCK60TtY1NjA-z3w@mail.gmail.com>
X-UI-Message-Type: mail
X-Priority: 3
X-Provags-ID: V03:K1:M+Wczg6xibChkLBlZ6jBHM09ldnrlDSgvBMUuHNHA/PWgN+QoD8RSVsJEkBI5yM36V/6W
CZu0Yv897NYZoDuwI0MXz+7cJplQsNdhZrSpYQpFSCpHhp2WE7YxO8I0rQo8GqzgOY2+OYg9fEKL
wSb/HTf4Qymq6uZ+Md8W+sUkz9mMZ9kOxnuAVgyu1v9FKd2zVcr2T2w9O3rH7s/I0B7UHfCD6fZN
pN1wDFToi5b60JFqqJPS6qC3BWCrbxzT6EqD2gzivK0LkJSldo6c3TdN970FXaRd/cAFomxnx9Gp
+s=
X-UI-Out-Filterresults: notjunk:1;V03:K0:jDAs3t6XeIA=:2xLh4udxdHSjgri5VBdHH9
6KOPKEDDBFmi5JmhK3qPLQJiAFh6Zp5MOQA5uaJv0bO1927kL6DF5TRmWJI4iDFC3W9nLO2FC
HmanJ8Cly4fPsIlVpDYd9pG0Dy3gAQIwK2o79YYKqXF/nVPWVVqiI5Jv2hLU9aPlaKThcK4X7
PblsAFXFvFnMVJDLIT1FzzP2WsyzkDExQ0zHp9J7DzSYNEoDHCARHVwjujXh2lEIfjU/TQ/Q2
v275auxw/nd0jqySCxa6toJjcZfGWYzlrpCjyUdB+XMza9IbFdC2v/jpMqOz3pfGrCHfiNQdq
jnCqOTz/Rg1SIfDM2zxSPPii2kaPlXA8G9w4kTSDYDjOaGkZmy7Q10MlP17mJao5JIOQssEXw
bK1ceDn1J/3xoCs9jOF/aPXhUHivQDldGMEXXO1fuujCTOZsUYsjvOm88A4YVzko2e0C28NR/
KkPyzWKuAfk8Jd7tz+WNhKNUNlAKrJ/uu3K1TqeYwQRP67Nkm0NKzemcRoM8ftbdnUr47S9Ot
HhpYm0K7pp41PmVzHx8GMkBHNEyUZcRzfjJR7SnelZRmrHaExo8LWlgBcxOrwT9KWoP8N86J/
aD/YOsitqjiKI=
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:45:32 -0000
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Under the assumption that 41kb space for transaction with zero fee should be enough, it does not break CPFP: The miner can throw out other transactions to make space for all parent transactions he needs. Please note: The incentive for miners is not to have 41kb filled with zero fees. The incentive is to fill all space with highest possible fee per byte transactions. (if necessary we could change the constant in the formula from 1.1 to 1.2 that would modify the space for zero fee transactions to 79kb)
<div> </div>
<div>Regards,</div>
<div>
<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> Montag, 08. April 2019 um 00:11 Uhr<br/>
<b>Von:</b> "Bernd Jendrissek" <bitcoin@bpj-code.co.za><br/>
<b>An:</b> simondev1 <random@gmx.ch>, "Bitcoin Protocol Discussion" <bitcoin-dev@lists.linuxfoundation.org><br/>
<b>Betreff:</b> Re: [bitcoin-dev] new BIP: Self balancing between excessively low/high fees and block size</div>
<div name="quoted-content">On Sun, 7 Apr 2019 at 17:45, simondev1 via bitcoin-dev<br/>
<bitcoin-dev@lists.linuxfoundation.org> wrote:<br/>
> ==Implementation==<br/>
> Sort transactions by FeeInSatoshiPerByte (lowest first)<br/>
> 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/>
> If this is valid for each transaction then the blocksize is valid.<br/>
<br/>
Doesn't this break CPFP? I think to avoid that you'll need to rework<br/>
your proposed algorithm to treat chains of transactions as a group.<br/>
(And note that you could have multiple transactions in one block that<br/>
depend on the same "parent" transaction, also in the same block.)</div>
</div>
</div>
</div></div></body></html>
|