John Dillon [ARCHIVE] on Nostr: 📅 Original date posted:2013-06-10 📝 Original message:-----BEGIN PGP SIGNED ...
📅 Original date posted:2013-06-10
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Mon, Jun 10, 2013 at 8:14 AM, Melvin Carvalho
<melvincarvalho at gmail.com> wrote:
> -1
>
> Firstly I appreciate the ingenious thought that went into this post.
>
> However, Bitcoin's fundamental philosophy was one CPU one vote.
Indeed it was. Which is why as GPU's came onto the scene Satoshi was strongly
against them. I have to wonder what he thinks of ASICs where just a handful of
companies control the supply of Bitcoin hashing power.
Satoshi also never forsaw pools, which are why just 2 or 3 people control the
majority of Bitcoin hashing power.
> The asymmetry lies in psychological terms, in that new defaults tend to be
> adopted 80% of the time, so core devs have disproportionate amount of power
> as things stand.
That's why I'm very clear that doing nothing is a vote for the status quo. Of
course wallet authors can do what they want to try to get users to vote
according to their wishes, or for that matter simply steal your vote, but we
already must put a lot of faith into wallets to not steal our funds.
> Unless there's a very good reason not to, e.g. miners are clearly abusing
> the system, we should stick with 1 CPU one vote.
People are proposing we put control of the blocksize entirely into the hands of
miners, yet we all have an interest in auditing the blocks miners produce.
There must be balance.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJRtY2jAAoJEEWCsU4mNhiPQEsH/0VNA7aJYdUbJjTnIiKoaCv3
JtWS1MKHjAJE6ZPDt+T/QPkEdZI4kNz3DGcZL6EDJtvZxZHfvEIaZDF1gpaH6OkC
oIZ0PkFPOxi0cncuAvT/a770evu7LzuT6fisY3EgGnlHujLQZ47LEa73Xo7pJVc7
RJHamGwkj+3HZRIuZIAn87qws/zRyTx5SXvb56xCKb0oxE4ZO0dn+8/nNSPWw13i
p3LpLlEQBBu+Du2nPSQupRjkz4MPP8v9EYefV5cjtNBK7ufAvA64OnwKB5dST+h+
N/vBcj3EIj/WEOf4myGcVxKp+skJ2SJDwxLigevgkKYPDNTVfXIverdXB0ANrQA=
=c8iU
-----END PGP SIGNATURE-----
Published at
2023-06-07 15:03:05Event JSON
{
"id": "25d0950afbfd9c85f7d39ca491528d69be1803539eb91234177c70707d1d791f",
"pubkey": "a0b592adfee20cad7bb28c238a9fc1fccf4511a458be8e3d96b00c914c8c3564",
"created_at": 1686150185,
"kind": 1,
"tags": [
[
"e",
"9c65e0538c0c65dd524896d67b9a9f484c5068051e57f2d48f8752479be057b1",
"",
"root"
],
[
"e",
"55e63157da50faef3d214d95d9dcf5571bda671ef080909482fb33fd5cf32fb5",
"",
"reply"
],
[
"p",
"e316966328c4cb66c34719ef9a7b3bc54ef601663ad4ab06185991237735aa19"
]
],
"content": "📅 Original date posted:2013-06-10\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nOn Mon, Jun 10, 2013 at 8:14 AM, Melvin Carvalho\n\u003cmelvincarvalho at gmail.com\u003e wrote:\n\u003e -1\n\u003e\n\u003e Firstly I appreciate the ingenious thought that went into this post.\n\u003e\n\u003e However, Bitcoin's fundamental philosophy was one CPU one vote.\n\nIndeed it was. Which is why as GPU's came onto the scene Satoshi was strongly\nagainst them. I have to wonder what he thinks of ASICs where just a handful of\ncompanies control the supply of Bitcoin hashing power.\n\nSatoshi also never forsaw pools, which are why just 2 or 3 people control the\nmajority of Bitcoin hashing power.\n\n\u003e The asymmetry lies in psychological terms, in that new defaults tend to be\n\u003e adopted 80% of the time, so core devs have disproportionate amount of power\n\u003e as things stand.\n\nThat's why I'm very clear that doing nothing is a vote for the status quo. Of\ncourse wallet authors can do what they want to try to get users to vote\naccording to their wishes, or for that matter simply steal your vote, but we\nalready must put a lot of faith into wallets to not steal our funds.\n\n\u003e Unless there's a very good reason not to, e.g. miners are clearly abusing\n\u003e the system, we should stick with 1 CPU one vote.\n\nPeople are proposing we put control of the blocksize entirely into the hands of\nminers, yet we all have an interest in auditing the blocks miners produce.\nThere must be balance.\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.11 (GNU/Linux)\n\niQEcBAEBCAAGBQJRtY2jAAoJEEWCsU4mNhiPQEsH/0VNA7aJYdUbJjTnIiKoaCv3\nJtWS1MKHjAJE6ZPDt+T/QPkEdZI4kNz3DGcZL6EDJtvZxZHfvEIaZDF1gpaH6OkC\noIZ0PkFPOxi0cncuAvT/a770evu7LzuT6fisY3EgGnlHujLQZ47LEa73Xo7pJVc7\nRJHamGwkj+3HZRIuZIAn87qws/zRyTx5SXvb56xCKb0oxE4ZO0dn+8/nNSPWw13i\np3LpLlEQBBu+Du2nPSQupRjkz4MPP8v9EYefV5cjtNBK7ufAvA64OnwKB5dST+h+\nN/vBcj3EIj/WEOf4myGcVxKp+skJ2SJDwxLigevgkKYPDNTVfXIverdXB0ANrQA=\n=c8iU\n-----END PGP SIGNATURE-----",
"sig": "589f7732e16c8541d4824d2cf19d8f57dc057c4a3c5b06bcb7b8e8a35cb685435446d4fa54564c82aed921dc99dae54f4e8772763804b3dfbf6c26e1a39f9063"
}