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
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id CB0A7ACC
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 27 Jun 2015 17:37:30 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148098.authsmtp.com (outmail148098.authsmtp.com
[62.13.148.98])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 10F0E198
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 27 Jun 2015 17:37:29 +0000 (UTC)
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5RHbShY078668;
Sat, 27 Jun 2015 18:37:28 +0100 (BST)
Received: from muck (cpe-74-66-142-58.nyc.res.rr.com [74.66.142.58])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5RHbPcR047785
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Sat, 27 Jun 2015 18:37:27 +0100 (BST)
Date: Sat, 27 Jun 2015 13:37:24 -0400
From: Peter Todd <pete@petertodd.org>
To: Benjamin <benjamin.l.cordes@gmail.com>
Message-ID: <20150627173724.GA30546@muck>
References: <CALgxB7udA85BWetBGc-RN=72ZtVPK9Q5HW8YRDKA08M38XqJqQ@mail.gmail.com>
<1EF70EBC-8BB8-4A93-8591-52B2B0335F6C@petertodd.org>
<CALgxB7usetoaNCObhG36TrdYgKuP4TSPPNkGatvim1oWUMxaeQ@mail.gmail.com>
<20150627172011.GB18729@muck>
<CAOoPuRZrV_8XJbCbHMEWAfoKYc+OSQQMuhgESgG2JD2nEHoyvQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL"
Content-Disposition: inline
In-Reply-To: <CAOoPuRZrV_8XJbCbHMEWAfoKYc+OSQQMuhgESgG2JD2nEHoyvQ@mail.gmail.com>
X-Server-Quench: 2e16903e-1cf3-11e5-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdAUUEkAaAgsB AmMbWlxeU1p7W2s7 bA5PawNDY05MQQBi
T01BRU1TWkFtY2RT Zk18Uh11cA1DNn9w ZERiEHIOXUJzdUUo
X08HQ24bZGY1bX1N U0leagNUcgZDfk5E bwQuUz1vNG8XDSg5
AwQ0PjZ0MThBHWx8 CjkXKkoVWksHVhU7 QggYGjAuBkBNWyJ7
MxwrYnQYG00Sen4z I1ZpfVMdMgN6
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 74.66.142.58/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] A Proposed Compromise to the Block Size Limit
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Sat, 27 Jun 2015 17:37:30 -0000
--vtzGhvizbBRQ85DL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Jun 27, 2015 at 07:26:00PM +0200, Benjamin wrote:
> "Thus we have a fixed capacity system where access is mediated by supply
> and demand transaction fees."
>=20
> There is no supply and demand. That would mean users would be able to ada=
pt
> fees and get different quality of service depending on current capacity.
> For example if peak load is 10x average load, then at those times fees
> would be higher and users would delay transactions to smooth out demand.
That's exactly how Bitcoin works already. See my article on how
transaction fees work for more details:
https://gist.github.com/petertodd/8e87c782bdf342ef18fb
--=20
'peter'[:-1]@petertodd.org
0000000000000000007fc13ce02072d9cb2a6d51fae41fefcde7b3b283803d24
--vtzGhvizbBRQ85DL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJVjt9SXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwMDdmYzEzY2UwMjA3MmQ5Y2IyYTZkNTFmYWU0MWZlZmNk
ZTdiM2IyODM4MDNkMjQvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udxv6gf/ZjW7DdQnB+922NkYFBUmoYEV
AqNGe2RWHRByYLqht1WhY16H+hevNrlWkuAe0TbnQGpXS9XaTTY/myw4rmi73YGK
j1VGhoGOhirjOhjrQGEmyO4yOCuQEkMSNS8C0NpNOjCbdB7hlJF+MqF7DQxI/zot
oJ4Z+Pz8BnZWmvtWmZ7hwdkqhyDlcGhPSUXDw5Bx3R/YiLzBC2tCamexYQTRTqqq
nX+WqLxHLMBk5KgmSjJaQOuYFMs2nDlN3vs3YLIcl2w9GI/8/85DILxtU6/80Afu
GsUqGY4WGJO2SNDazzCKbEgBG8jJsDFqD+u/ydSdMcSnfoNI2hM1j06wZvDwjg==
=NMII
-----END PGP SIGNATURE-----
--vtzGhvizbBRQ85DL--
|
