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
142
143
144
145
146
147
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1VhOwS-0007yF-BN
for bitcoin-development@lists.sourceforge.net;
Fri, 15 Nov 2013 19:20:32 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.84 as permitted sender)
client-ip=62.13.149.84; envelope-from=pete@petertodd.org;
helo=outmail149084.authsmtp.net;
Received: from outmail149084.authsmtp.net ([62.13.149.84])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1VhOwQ-000101-5c for bitcoin-development@lists.sourceforge.net;
Fri, 15 Nov 2013 19:20:32 +0000
Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237])
by punt8.authsmtp.com (8.14.2/8.14.2) with ESMTP id rAFJK219041005;
Fri, 15 Nov 2013 19:20:02 GMT
Received: from petertodd.org (petertodd.org [174.129.28.249])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id rAFJJutB026112
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Fri, 15 Nov 2013 19:19:59 GMT
Date: Fri, 15 Nov 2013 14:19:56 -0500
From: Peter Todd <pete@petertodd.org>
To: Michael Gronager <gronager@ceptacle.com>
Message-ID: <20131115191956.GB29469@petertodd.org>
References: <528367F5.9080303@ceptacle.com> <20131115103246.GB17034@savin>
<528609E2.2050107@ceptacle.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="R3G7APHDIzY6R/pk"
Content-Disposition: inline
In-Reply-To: <528609E2.2050107@ceptacle.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: eb54f025-4e2a-11e3-94fa-002590a135d3
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdwcUFloCAgsB AmUbWl1eUVR7XGo7 ag1VcwRfa1RMVxto
VEFWR1pVCwQmQ213 fGRbFmtydQNHeXw+ bEdlWT4ODkF+I0Z/
R1NQQG9XeGZhPWMC WUQOJh5UcAFPdx8U a1N6AHBDAzANdhES
HhM4ODE3eDlSNilR RRkIIFQOdA4mADM6 DwsDGC0rEFdNQiQ1
Lhk7LxYSEUtZOUw2 OkYlUE4ZNBlwQgNZ BURQBCYLb1dJEWIh
Ch5cQV9cHjpHQhBG CwElZRZWDyZbVSdv Dk9CQBIUCjFIOCAN
X-Authentic-SMTP: 61633532353630.1024:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 174.129.28.249/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: petertodd.org]
0.0 LOTS_OF_MONEY Huge... sums of money
X-Headers-End: 1VhOwQ-000101-5c
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Even simpler minimum fee calculation
formula: f > bounty*fork_rate/average_blocksize
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: Fri, 15 Nov 2013 19:20:32 -0000
--R3G7APHDIzY6R/pk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Nov 15, 2013 at 12:47:46PM +0100, Michael Gronager wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 15/11/13, 11:32 , Peter Todd wrote:
>=20
> > alpha =3D (1/113)*600s/134kBytes =3D 39.62uS/byte =3D 24kB/second
> >=20
> > Which is atrocious...=20
>=20
> alpha =3D P_fork*t_block/S =3D 1/113*454000/134 =3D 29ms/kb
Huh? Where did 454000 come from?
> > , which shows you how little attention they are paying to
> > optimizing profits. Right now mining pulls in $1.8 million/day, so
> > that's up to $16k wasted.
>=20
> yup, but the relevant comparison is not 16k vs 1.8m, but the pool
> operator earnings which are on the order of 1% of the 1.8m so it is 18k
> vs 16k - I wouldn't mind doubling my income...
That's only true for a PPS pool though, not the more usual pools that
pay relative to blocks actually found. Heh, actually, that might be part
of the problem... also doesn't help how varience is going to make
noticing 1% hard.
> > In
> > theory anyway, could just as easily be the case that larger pools have
> > screwed up relaying still such that p2pool's forwarding wins.
>=20
> Yeah, we should resurrect p2pool ;)
P2Pool has 1% hashing power right now; I mine on it myself with what
little hashing power I have.
The more interesting thing is how do you grow P2Pool - requiring a full
node is going to make that tricky. Also the once we start adding more
efficient block propagation by transmitting headers + txids p2pool's
current advantage goes away.
--=20
'peter'[:-1]@petertodd.org
0000000000000005fbc1840bbd5bd71d4d6cd2930e20da9e697710f58bd4f69d
--R3G7APHDIzY6R/pk
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJShnPbAAoJEBmcgzuo5/CF2D0IALD9Wmv4BTFzehhD69+oR2NX
hAKs+Lc6lvcCQKcMz/RcvY2Rx/iJzbqlAi9OtV+Fl9hfteduyCYdk0FnXboYuZzf
oKkKumsSAkachK991d7cGWXq393UzxORkZx+PP004m/leqeAdsGGmdaBDxVzSBcQ
eNO00+PrwdjSmzOETO4+IMZemGOUZN9EKc+6KiAjVr1PHXF5/gilS2w1hiymseTB
Z0o0/ICQSWykWwSwDc0L+Nra50DwMQ+1NLTm/6pkW6yfoRlsU5T0zhZRCj3DgKv5
Dfvd8yUQPkb251l4NgPHFt69PSGbny5HhvbrDZUy+kBN0ypUVz6pN7++SMCYeqg=
=kbnv
-----END PGP SIGNATURE-----
--R3G7APHDIzY6R/pk--
|
