Big Barry Bitcoin on Nostr: A malicious miner can come in a few forms: 1. They are trying to censor the network ...
A malicious miner can come in a few forms:
1. They are trying to censor the network and have sneakily amassed over 51% of the hash power so it is working.
2. They are attempting to create blocks with invalid transactions or just plainly not following rules yet attempting to pass off their data as a bitcoin block.
Thats probably most of the cases, othet cases kind of fit into one or the other.
In case 1, we "kick them out" by introducing a new rule and roll it out. This isn't a simple task, it will involve convincing people that this is the most conservative way to work around these people while not leading down a slippery slope of just introducing a way to censor people.
The other way we kick them out is by rallying the people to run more nodes and mjners, to outmine the bad actors.
Eventually, the cost to censor will be too much and the enemy will run out of funds.
For case 2, the system already works. Even if the malicious miner had 90% hash rate, our software rejects anything that is considered invalid so these blocks are ignored by users. Some users who rely on custodians or third party nodes may be affected, but majority of economic activity and therefore the most fees to collect will only be collectable by miners who also don't mjne on invalid blocks.
The attacker will quickly realise they are wasting time, energy and money and even if not, we are never affected and more people who use custodial systems start to learn to use Bitcoin natively.
Published at
2024-10-31 19:12:38Event JSON
{
"id": "a3a8c78ca10175e81d13f2c70fe7ce2232937f8144863f7ba5f8c64ca97fcb93",
"pubkey": "0d97beae567fcec9c6574f1c6ef6126ea969d4992c3198e51c0fac52c5274a14",
"created_at": 1730401958,
"kind": 1,
"tags": [
[
"e",
"f210a88f950f32d5bea6934856ad3f43b5deab9133708a227382f5aaf7adc1d7",
"",
"root"
],
[
"p",
"9f83869cafcfe6d34e30d46044bc81dd240858b29a1f6bf12e44efc8c6d53766"
]
],
"content": "A malicious miner can come in a few forms:\n\n1. They are trying to censor the network and have sneakily amassed over 51% of the hash power so it is working.\n\n2. They are attempting to create blocks with invalid transactions or just plainly not following rules yet attempting to pass off their data as a bitcoin block.\n\nThats probably most of the cases, othet cases kind of fit into one or the other.\n\nIn case 1, we \"kick them out\" by introducing a new rule and roll it out. This isn't a simple task, it will involve convincing people that this is the most conservative way to work around these people while not leading down a slippery slope of just introducing a way to censor people.\n\nThe other way we kick them out is by rallying the people to run more nodes and mjners, to outmine the bad actors.\n\nEventually, the cost to censor will be too much and the enemy will run out of funds.\n\nFor case 2, the system already works. Even if the malicious miner had 90% hash rate, our software rejects anything that is considered invalid so these blocks are ignored by users. Some users who rely on custodians or third party nodes may be affected, but majority of economic activity and therefore the most fees to collect will only be collectable by miners who also don't mjne on invalid blocks.\n\nThe attacker will quickly realise they are wasting time, energy and money and even if not, we are never affected and more people who use custodial systems start to learn to use Bitcoin natively.",
"sig": "da3576e9d20289b366ec344691eebf0c6b3233d35daafc523e8c7c83629d3f2bb17115fd3d4a0454eb824355b10499a050f8010307f1a3cec4f899ec447d4d90"
}