jl2012 at xbt.hk [ARCHIVE] on Nostr: 📅 Original date posted:2015-09-28 📝 Original message:Mike Hearn via bitcoin-dev ...
📅 Original date posted:2015-09-28
📝 Original message:Mike Hearn via bitcoin-dev 於 2015-09-28 11:38 寫到:
> My point about IsStandard is that miners can and do bypass it,
> without expecting that to carry financial consequences or lower the
> security of other users. By making it so a block which includes
> non-standard transactions can end up being seen as invalid, you are
> increasing the risk of accidents that carry financial consequences.
Bypassing IsStandard should be considered as an "expert mode". The
message should be "don't bypass it unless you understand what you are
doing".
By the way, miners are PAID to protect the network. It is their greatest
responsibility to follow the development and keep their software up to
date.
> How do ordinary Bitcoin users benefit from this rollout strategy? Put
> simply, what is the point of this whole complex soft fork endeavour?
Let me try to answer this question. Softfork is beneficial to non-mining
full nodes as they will follow the majority chain. In the case of a
hardfork (e.g. BIP101), non-upgrading full nodes will insist to follow
the minority chain. (unless you believe that all non-miner should use an
SPV client)
Put it in a different angle. In a softfork, the new fork is a persistent
95% attack against the old fork, which will force all in-cooperating
miners to join (or leave). In a hardfork, however, there is no mechanism
to stop the old fork and we may have 2 chains co-exist for a long time.
Although it is not mentioned in the whitepaper, the ability to softfork
is a feature of Bitcoin. Otherwise, we won't have these OP_NOPs and the
original OP_RETURN.
Published at
2023-06-07 17:41:35Event JSON
{
"id": "e85d5c0615167f8149b9f52ebf2f4823aefa2af01dec10d2179289d3f3d96c59",
"pubkey": "b61e2e7ccbf4abd7f49715c62f4ac7a93cbdd5ead0316279c5f5fe9b18dd0aaa",
"created_at": 1686159695,
"kind": 1,
"tags": [
[
"e",
"f5bb1bf208994917ac3ec4154383520df2a8573df815c54d28bae4e41ef024c8",
"",
"root"
],
[
"e",
"6f1ffc93e5e37e2a41520b85293bd9a9ff30bf900a7c7dc910036533ca0e15bc",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2015-09-28\n📝 Original message:Mike Hearn via bitcoin-dev 於 2015-09-28 11:38 寫到:\n\n\u003e My point about IsStandard is that miners can and do bypass it,\n\u003e without expecting that to carry financial consequences or lower the\n\u003e security of other users. By making it so a block which includes\n\u003e non-standard transactions can end up being seen as invalid, you are\n\u003e increasing the risk of accidents that carry financial consequences.\n\nBypassing IsStandard should be considered as an \"expert mode\". The \nmessage should be \"don't bypass it unless you understand what you are \ndoing\".\n\nBy the way, miners are PAID to protect the network. It is their greatest \nresponsibility to follow the development and keep their software up to \ndate.\n\n\n\n\u003e How do ordinary Bitcoin users benefit from this rollout strategy? Put\n\u003e simply, what is the point of this whole complex soft fork endeavour?\n\nLet me try to answer this question. Softfork is beneficial to non-mining \nfull nodes as they will follow the majority chain. In the case of a \nhardfork (e.g. BIP101), non-upgrading full nodes will insist to follow \nthe minority chain. (unless you believe that all non-miner should use an \nSPV client)\n\nPut it in a different angle. In a softfork, the new fork is a persistent \n95% attack against the old fork, which will force all in-cooperating \nminers to join (or leave). In a hardfork, however, there is no mechanism \nto stop the old fork and we may have 2 chains co-exist for a long time.\n\nAlthough it is not mentioned in the whitepaper, the ability to softfork \nis a feature of Bitcoin. Otherwise, we won't have these OP_NOPs and the \noriginal OP_RETURN.",
"sig": "5dd78985a7e6befdce9651ae3aa78d699b3b3a8a2600ad3ac7b1243e2a6f151110933f6b513db46a009ac33fd0dbe81208e330edfe5ac2da5cee5aa6ac792915"
}