📅 Original date posted:2015-09-18
📝 Original message:On 18/09/15 15:17, Rune Kjær Svendsen via bitcoin-dev wrote:
> Bitcoin does not function if the majority of mining power is dishonest. There is no way around that. It’s how proof-of-work functions.
None of those statements are true.
If a majority of Bitcoin miners are mining invalid blocks, then they
aren't Bitcoin miners any more and are no longer relevant to the Bitcoin
consensus.
There does exist a problem that light clients aren't always able to tell
the difference between chains that are valid and chains that are not
valid, but it's is possible to create simple proofs that would do so:
https://gist.github.com/justusranvier/451616fa4697b5f25f60
If those changes would be implemented, then any node that knew a chain
was invalid could produce a compact proof that anyone else in the
network could verify, regardless of how much proof of work was used to
create the invalid chain.
Committed UTXO sets would need safe to rely upon if a similar set of
proofs that a particular set was invalid existed.
--
Justus Ranvier
Open Bitcoin Privacy Project
http://www.openbitcoinprivacyproject.org/
justus at openbitcoinprivacyproject.org
E7AD 8215 8497 3673 6D9E 61C4 2A5F DA70 EAD9 E623
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xEAD9E623.asc
Type: application/pgp-keys
Size: 18442 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150918/69ac0ec4/attachment.bin>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150918/69ac0ec4/attachment.sig>;
Justus Ranvier [ARCHIVE] /
npub1k2…9qd6m
2023-06-07 17:40:59
in reply to nevent1q…zqnr
Author Public Key
npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6mPublished at
2023-06-07 17:40:59Event JSON
{
"id": "3b43e58307923c235575edc4a1ba89525b38412c979d1318022a132db60d144d",
"pubkey": "b2b39b6f2c86908d3da9f500193abd5757b21cac328f838800a48c4d557c10dd",
"created_at": 1686159659,
"kind": 1,
"tags": [
[
"e",
"7fadb5378c1c44e78cc5de59daa2e951bce7b919506a3d6cff2bcf05fa79c75d",
"",
"root"
],
[
"e",
"5d6f3e84e23976881afdfe2d8399e77930faff21f57afbf8c15b97f5437c0ceb",
"",
"reply"
],
[
"p",
"43d409a3ebd823071d562a2252a9126d5cba7aee3ffea64cf3e28e252af0a8e8"
]
],
"content": "📅 Original date posted:2015-09-18\n📝 Original message:On 18/09/15 15:17, Rune Kjær Svendsen via bitcoin-dev wrote:\n\u003e Bitcoin does not function if the majority of mining power is dishonest. There is no way around that. It’s how proof-of-work functions.\n\n\nNone of those statements are true.\n\nIf a majority of Bitcoin miners are mining invalid blocks, then they\naren't Bitcoin miners any more and are no longer relevant to the Bitcoin\nconsensus.\n\nThere does exist a problem that light clients aren't always able to tell\nthe difference between chains that are valid and chains that are not\nvalid, but it's is possible to create simple proofs that would do so:\n\nhttps://gist.github.com/justusranvier/451616fa4697b5f25f60\n\n\nIf those changes would be implemented, then any node that knew a chain\nwas invalid could produce a compact proof that anyone else in the\nnetwork could verify, regardless of how much proof of work was used to\ncreate the invalid chain.\n\nCommitted UTXO sets would need safe to rely upon if a similar set of\nproofs that a particular set was invalid existed.\n\n-- \nJustus Ranvier\nOpen Bitcoin Privacy Project\nhttp://www.openbitcoinprivacyproject.org/\njustus at openbitcoinprivacyproject.org\nE7AD 8215 8497 3673 6D9E 61C4 2A5F DA70 EAD9 E623\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: 0xEAD9E623.asc\nType: application/pgp-keys\nSize: 18442 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150918/69ac0ec4/attachment.bin\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 801 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150918/69ac0ec4/attachment.sig\u003e",
"sig": "217929becc5b4d3cb6a55fbac49e9df1c8f6aa5ba7cffaa699305990d1dcaa89b25123ff2385f7a7c90b7d93d9d8e9daaab2708624cc0e68e1db52d4ebc45de9"
}