đ
Original date posted:2013-11-13
đ Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Fri, Nov 8, 2013 at 4:21 PM, Goss, Brian C., M.D.
<Goss.Brian at 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-----
John Dillon [ARCHIVE] /
npub15zâŚkn0zr
2023-06-07 15:09:19
in reply to nevent1qâŚcv3d
Author Public Key
npub15z6e9t07ugx267aj3s3c487pln852ydytzlgu0vkkqxfznyvx4jq4kn0zrPublished at
2023-06-07 15:09:19Event JSON
{
"id": "9eeacf8f0c828197e605202cd8c188e9c7f0b4d3e4f8222124c7fbf3e74f1b3c",
"pubkey": "a0b592adfee20cad7bb28c238a9fc1fccf4511a458be8e3d96b00c914c8c3564",
"created_at": 1686150559,
"kind": 1,
"tags": [
[
"e",
"2395d270931e730ab863e8a0bae3a43f59dd1c7ff3c778130d797b83500c7a2f",
"",
"root"
],
[
"e",
"bc735aaff34c903b36222dc974255c953ad510f66177558d5d90e936e61b2e09",
"",
"reply"
],
[
"p",
"44617e3045738188ba48183b720c7191b8bd4f8317ecc642f6085ba0325d67e4"
]
],
"content": "đ
Original date posted:2013-11-13\nđ Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nOn Fri, Nov 8, 2013 at 4:21 PM, Goss, Brian C., M.D.\n\u003cGoss.Brian at mayo.edu\u003e wrote:\n\u003e Peter,\n\u003e\n\u003e What is the propagation time within a pool? If my pool is made up of a ton\n\u003e of fancy ASICs connected by 300 baud modems, how does that affect your\n\u003e analysis (ie, Q for a mining pool is effectively a function of time as\n\u003e well)?\n\nThe propagation time you're thinking of is from the pool to the miner, and even\nnow that is significant for pools that do not pay for stale shares. I remember\nan Australian pool mentioning that problem on their website as a reason for the\npools existence.\n\nI would expect selfish mining, as well as orphans becoming more important in\ngeneral, to centralize the physical location of hashing power too. If the 100ms\ndelay to your pool impacts profits you'll have an incentive to locate your\nmining equipment physically closer to the pool. The next step is pools wanting\nto physically locate themselves closer to other pools.\n\nIt would not be good if all Bitcoin mining was done in Iceland...\n\n\u003e Brian\n\u003e P.S. I hope these are not ignorant questions; if they are, please feel free\n\u003e to disregard!\n\nNot ignorant at all IMO.\n\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.11 (GNU/Linux)\n\niQEcBAEBCAAGBQJSg+CpAAoJEEWCsU4mNhiPufwIAKNpBBvlRvSQZOzMJvghG7fX\nlCNliohDKw9kdKJJjN1T73Ssl06wGbBe881k4c4r7fHeNDRQZbrFsj+uBsFyUhmy\nCF70KiOKuowDlWwyWMxZbbyinK0mEKC7J/hJVOt15FHubLnq71Utb+I2L7seyHlo\n2E2byG4UnofoD5L+hGzfD6FJ/zYEHtTKgFw7Y1+ZSmAxlIcdrcpH7tPmUzFD7JPi\nRnaK1BH7hpM6FyZQUhSC/tW7mYswNEasvouBE4V1vSySZb6S43kiED2Q4uH3W0+A\nUtbyRQ7yT3BOLGB2OO/L92tg6S7WRyMtvQoevJkEIAnUywD3YWaZnBbf0IM4LWg=\n=6750\n-----END PGP SIGNATURE-----",
"sig": "89d5f35f08d64db474ff98beb5e0ca6ddda0bd0179720de7255090f455815276986e8f19f966beeba255a727daf6b1719abf9bddad7990d57a5e4eb34465170a"
}