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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tier.nolan@gmail.com>) id 1YsU8C-0006ER-3p
for bitcoin-development@lists.sourceforge.net;
Wed, 13 May 2015 10:43:16 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.176 as permitted sender)
client-ip=209.85.220.176; envelope-from=tier.nolan@gmail.com;
helo=mail-qk0-f176.google.com;
Received: from mail-qk0-f176.google.com ([209.85.220.176])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YsU8A-0002oc-Bh
for bitcoin-development@lists.sourceforge.net;
Wed, 13 May 2015 10:43:16 +0000
Received: by qkgx75 with SMTP id x75so24874294qkg.1
for <bitcoin-development@lists.sourceforge.net>;
Wed, 13 May 2015 03:43:08 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.140.132.80 with SMTP id 77mr27184677qhe.36.1431513788802;
Wed, 13 May 2015 03:43:08 -0700 (PDT)
Received: by 10.140.85.241 with HTTP; Wed, 13 May 2015 03:43:08 -0700 (PDT)
In-Reply-To: <CAAS2fgQRS7w7RRNXVK_+=4CQ7=AWxWQQ7+Tf4tNUPTTZOf7rEQ@mail.gmail.com>
References: <16096345.A1MpJQQkRW@crushinator>
<CAOG=w-szbLgc1jLpkE_uMa3bkFTi-RiBEaQ6Y-u5aKLBC2HvUg@mail.gmail.com>
<CAAS2fgQRS7w7RRNXVK_+=4CQ7=AWxWQQ7+Tf4tNUPTTZOf7rEQ@mail.gmail.com>
Date: Wed, 13 May 2015 11:43:08 +0100
Message-ID: <CAE-z3OUzYZDvsOYEDT229vnvNBa9ntW+86O3uA-K5-KaneMF_g@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c07daadf72520515f44664
X-Spam-Score: 2.5 (++)
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
(tier.nolan[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
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
1.9 MALFORMED_FREEMAIL Bad headers on message from free email service
0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YsU8A-0002oc-Bh
Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step
function
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 10:43:16 -0000
--001a11c07daadf72520515f44664
Content-Type: text/plain; charset=UTF-8
On Sat, May 9, 2015 at 4:36 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> An example would
> be tx_size = MAX( real_size >> 1, real_size + 4*utxo_created_size -
> 3*utxo_consumed_size).
This could be implemented as a soft fork too.
* 1MB hard size limit
* 900kB soft limit
S = block size
U = UTXO_adjusted_size = S + 4 * outputs - 3 * inputs
A block is valid if S < 1MB and U < 1MB
A 250 byte transaction with 2 inputs and 2 outputs would have an adjusted
size of 252 bytes.
The memory pool could be sorted by fee per adjusted_size.
Coin selection could be adjusted so it tries to have at least 2 inputs
when creating transactions, unless the input is worth more than a threshold
(say 0.001 BTC).
This is a pretty weak incentive, especially if the block size is
increased. Maybe it will cause a "nudge"
--001a11c07daadf72520515f44664
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, May 9, 2015 at 4:36 AM, Gregory Maxwell <span dir=3D"ltr"><<a href=
=3D"mailto:gmaxwell@gmail.com" target=3D"_blank">gmaxwell@gmail.com</a>>=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">An example would<br>
be tx_size =3D MAX( real_size >> 1,=C2=A0 real_size + 4*utxo_created_=
size -<br>
3*utxo_consumed_size).=C2=A0</blockquote><div><br></div><div>This could be =
implemented as a soft fork too.<br><br></div><div>* 1MB hard size limit<br>=
</div><div>* 900kB soft limit<br><br></div><div>S =3D block size<br></div><=
div>U =3D UTXO_adjusted_size =3D S + 4 * outputs - 3 * inputs<br><br></div>=
<div></div><div>A block is valid if S < 1MB and U < 1MB<br><br>A 250 =
byte transaction with 2 inputs and 2 outputs would have an adjusted size of=
252 bytes.<br></div><div><br></div><div>The memory pool could be sorted by=
fee per adjusted_size.=C2=A0 <br></div><div><br></div><div>=C2=A0Coin sele=
ction could be adjusted so it tries to have at least 2 inputs when creating=
transactions, unless the input is worth more than a threshold (say 0.001 B=
TC).<br><br></div><div>This is a pretty weak incentive, especially if the b=
lock size is increased.=C2=A0 Maybe it will cause a "nudge"<br></=
div></div></div></div>
--001a11c07daadf72520515f44664--
|
