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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <john.dillon892@googlemail.com>) id 1Vgh2d-0000Yz-Iv
for bitcoin-development@lists.sourceforge.net;
Wed, 13 Nov 2013 20:27:59 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of googlemail.com
designates 209.85.215.172 as permitted sender)
client-ip=209.85.215.172;
envelope-from=john.dillon892@googlemail.com;
helo=mail-ea0-f172.google.com;
Received: from mail-ea0-f172.google.com ([209.85.215.172])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vgh2c-00039n-NQ
for bitcoin-development@lists.sourceforge.net;
Wed, 13 Nov 2013 20:27:59 +0000
Received: by mail-ea0-f172.google.com with SMTP id h11so437050eaj.31
for <bitcoin-development@lists.sourceforge.net>;
Wed, 13 Nov 2013 12:27:52 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.15.24.142 with SMTP id j14mr8497918eeu.52.1384374472351;
Wed, 13 Nov 2013 12:27:52 -0800 (PST)
Received: by 10.223.135.132 with HTTP; Wed, 13 Nov 2013 12:27:52 -0800 (PST)
In-Reply-To: <FFE335820B1BFF4F8E8619F446F2D87F4C20067D@MSGPEXCEI32B.mfad.mfroot.org>
References: <FFE335820B1BFF4F8E8619F446F2D87F4C20067D@MSGPEXCEI32B.mfad.mfroot.org>
Date: Wed, 13 Nov 2013 20:27:52 +0000
Message-ID: <CAPaL=UWEwWOtLtj684jNAhpDV3C8rWZ+dUVC6FWMmWpARRzUOg@mail.gmail.com>
From: John Dillon <john.dillon892@googlemail.com>
To: "Goss, Brian C., M.D." <Goss.Brian@mayo.edu>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.3 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
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: googlemail.com]
-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
(john.dillon892[at]googlemail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (john.dillon892[at]googlemail.com)
-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
X-Headers-End: 1Vgh2c-00039n-NQ
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 1. Re: On the optimal block size and why
transaction fees are 8
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 Nov 2013 20:27:59 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Fri, Nov 8, 2013 at 4:21 PM, Goss, Brian C., M.D.
<Goss.Brian@mayo.edu> wrote:
> Peter,
>
> What is the propagation time within a pool? If my pool is made up of a ton
> of fancy ASICs connected by 300 baud modems, how does that affect your
> analysis (ie, Q for a mining pool is effectively a function of time as
> well)?
The propagation time you're thinking of is from the pool to the miner, and even
now that is significant for pools that do not pay for stale shares. I remember
an Australian pool mentioning that problem on their website as a reason for the
pools existence.
I would expect selfish mining, as well as orphans becoming more important in
general, to centralize the physical location of hashing power too. If the 100ms
delay to your pool impacts profits you'll have an incentive to locate your
mining equipment physically closer to the pool. The next step is pools wanting
to physically locate themselves closer to other pools.
It would not be good if all Bitcoin mining was done in Iceland...
> Brian
> P.S. I hope these are not ignorant questions; if they are, please feel free
> to disregard!
Not ignorant at all IMO.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJSg+CpAAoJEEWCsU4mNhiPufwIAKNpBBvlRvSQZOzMJvghG7fX
lCNliohDKw9kdKJJjN1T73Ssl06wGbBe881k4c4r7fHeNDRQZbrFsj+uBsFyUhmy
CF70KiOKuowDlWwyWMxZbbyinK0mEKC7J/hJVOt15FHubLnq71Utb+I2L7seyHlo
2E2byG4UnofoD5L+hGzfD6FJ/zYEHtTKgFw7Y1+ZSmAxlIcdrcpH7tPmUzFD7JPi
RnaK1BH7hpM6FyZQUhSC/tW7mYswNEasvouBE4V1vSySZb6S43kiED2Q4uH3W0+A
UtbyRQ7yT3BOLGB2OO/L92tg6S7WRyMtvQoevJkEIAnUywD3YWaZnBbf0IM4LWg=
=6750
-----END PGP SIGNATURE-----
|
