Peter Todd [ARCHIVE] on Nostr: š
Original date posted:2015-08-04 š Original message:-----BEGIN PGP SIGNED ...
š
Original date posted:2015-08-04
š Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 4 August 2015 17:30:28 GMT-04:00, Gavin Andresen via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>On Tue, Aug 4, 2015 at 2:41 PM, Dave Hudson via bitcoin-dev <
>bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>> Fundamentally a block maker (pool or aggregation of pools) does not
>orphan
>> its own blocks.
>
>
>Unless the block maker has an infinitely fast connection to it's
>hashpower
>OR it's hashpower is not parallelized at all, that's not strictly true
>--
>it WILL orphan its own blocks because two hashing units will find
>solutions
>in the time it takes to communicate that solution to the block maker
>and to
>the rest of the hashing units.
>
>That's getting into "how many miners can dance on the head of a pin"
>territory, though. I don't think we know whether the communication
>advantages of putting lots of hashing power physically close together
>will
>outweigh the extra cooling costs of doing that (or maybe some other
>tradeoff I haven't thought of). That would be a fine topic for another
>paper....
I'd suggest you do more research into how Bitcoin and mining works as the above has a number of serious misunderstandings.
Or, I could just point out the obvious rather than try to be polite: you know exactly why the above makes no sense as a reply to this thread and are deliberately lying.
If the situation is the latter, your conduct is toxic to the development mailing list discussion, not to mention a waste of all our time, and you should leave.
-----BEGIN PGP SIGNATURE-----
iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVwTKi
AAoJEMCF8hzn9Lnc47AH/0txNyw9dLdsfQOsNE14jLEcQifxOkaKLqTJV1O4gn6O
L4+T6rPo9pVLTBuVWcsm2A24R/gBL+pYaWgaIyk/3fbSRpg4GfVau0xxh54vQU6m
U4L7FPHsdZ2y67frv/+5ExJ2xrVuedhpTciTi2SqSE6C0fioO+YarH0Dvd8I5Wjx
f9GnmxLdKytoj2kUaoriSSxsUzMNzxVzq78jEmhMR85TGy73ApeLdgBC/pdNgxZa
oAQ0CXCMYgsE59HUOO05xFLazGxNh2epPADTbTTgoNQ9py38evlW254okhRmk9p9
v4i1yTzuv/Y6C0qw2RZcEiT/GTdvajkMKCidLEm3LbY=
=W/Ke
-----END PGP SIGNATURE-----
Published at
2023-06-07 17:32:48Event JSON
{
"id": "0aadfd7b295b905a84ecfd2960324857cf44e7977d5e60f4c8f34cbc27f41a71",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686159168,
"kind": 1,
"tags": [
[
"e",
"2da2e00d8e383de13f6ee6d9d66f9da48994b834188a0ae47ea0319febd85ff5",
"",
"root"
],
[
"e",
"df7e61e688013a7f98dc001c654d23d51c4b06773c60385dedafacdc0c10cc1d",
"",
"reply"
],
[
"p",
"857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4"
]
],
"content": "š
Original date posted:2015-08-04\nš Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\n\n\nOn 4 August 2015 17:30:28 GMT-04:00, Gavin Andresen via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003eOn Tue, Aug 4, 2015 at 2:41 PM, Dave Hudson via bitcoin-dev \u003c\n\u003ebitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e\u003e Fundamentally a block maker (pool or aggregation of pools) does not\n\u003eorphan\n\u003e\u003e its own blocks.\n\u003e\n\u003e\n\u003eUnless the block maker has an infinitely fast connection to it's\n\u003ehashpower\n\u003eOR it's hashpower is not parallelized at all, that's not strictly true\n\u003e--\n\u003eit WILL orphan its own blocks because two hashing units will find\n\u003esolutions\n\u003ein the time it takes to communicate that solution to the block maker\n\u003eand to\n\u003ethe rest of the hashing units.\n\u003e\n\u003eThat's getting into \"how many miners can dance on the head of a pin\"\n\u003eterritory, though. I don't think we know whether the communication\n\u003eadvantages of putting lots of hashing power physically close together\n\u003ewill\n\u003eoutweigh the extra cooling costs of doing that (or maybe some other\n\u003etradeoff I haven't thought of). That would be a fine topic for another\n\u003epaper....\n\nI'd suggest you do more research into how Bitcoin and mining works as the above has a number of serious misunderstandings.\n\nOr, I could just point out the obvious rather than try to be polite: you know exactly why the above makes no sense as a reply to this thread and are deliberately lying.\n\nIf the situation is the latter, your conduct is toxic to the development mailing list discussion, not to mention a waste of all our time, and you should leave.\n\n-----BEGIN PGP SIGNATURE-----\n\niQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVwTKi\nAAoJEMCF8hzn9Lnc47AH/0txNyw9dLdsfQOsNE14jLEcQifxOkaKLqTJV1O4gn6O\nL4+T6rPo9pVLTBuVWcsm2A24R/gBL+pYaWgaIyk/3fbSRpg4GfVau0xxh54vQU6m\nU4L7FPHsdZ2y67frv/+5ExJ2xrVuedhpTciTi2SqSE6C0fioO+YarH0Dvd8I5Wjx\nf9GnmxLdKytoj2kUaoriSSxsUzMNzxVzq78jEmhMR85TGy73ApeLdgBC/pdNgxZa\noAQ0CXCMYgsE59HUOO05xFLazGxNh2epPADTbTTgoNQ9py38evlW254okhRmk9p9\nv4i1yTzuv/Y6C0qw2RZcEiT/GTdvajkMKCidLEm3LbY=\n=W/Ke\n-----END PGP SIGNATURE-----",
"sig": "0397d2308348d5256c46ff26635720f494dfb850a95924d8d3dc62619413f9e32499eec9d4ce2929965f88162f57ac73677e18beea09ab644dfcdb4bc363c71e"
}