📅 Original date posted:2015-06-25
📝 Original message:On 6/24/2015 8:00 PM, Raystonn wrote:
>
> > Consensus-code changes are unanimous. They must be.
>
> Excellent. Now we are getting to some actual written rules. How about
> updating the BIP process documentation with this? Everyone should be
> able to read the rules of the coin they are buying.
>
> One moment though. Can you tell me how this particular rule came to
> be? The creator of Bitcoin violated this rule many times. So it must
> have been adopted after his departure. What process was followed to
> adopt this new rule? Was there consensus for it at the time? A huge
> portion of the user community is under the impression that Satoshi's
> written plans, some of which violate this new rule, will be
> implemented. So there certainly would not be consensus for this rule
> today.
>
Great question; very fair. I, for one, eagerly await Mark's answer.
I hope nobody forgot to tell adversaries totally outside the open source
ecosystem what the rules for hard forking changes are.
The Chinese miners have it right - we have to work together. If you
want to see who's trying, look at who has written a concrete BIP/code
vs. who hasn't; who has made changes in response to feedback, and who
hasn't.
Tom Harding [ARCHIVE] /
npub1ms…pmwjy
2023-06-07 15:40:24
in reply to nevent1q…9syd
Author Public Key
npub1msef5qkfwz4t7qacwxz775wgdtlytph78g2g2z903x90874u263sypmwjyPublished at
2023-06-07 15:40:24Event JSON
{
"id": "a7ebfae123c88e7f47f15caa905fb41ae253210f89d13e194a6847f6317eb121",
"pubkey": "dc329a02c970aabf03b87185ef51c86afe4586fe3a148508af898af3fabc56a3",
"created_at": 1686152424,
"kind": 1,
"tags": [
[
"e",
"3fe09b8bc3b13f27e42579b8ab63a325ab25d17e0571ce6b5f141d69b2abe4bf",
"",
"root"
],
[
"e",
"a642f5015fb7505adf0859d6636b3122bd53460d62a0cef5d58686cf2e867d95",
"",
"reply"
],
[
"p",
"238bb115101f2c05433c2b8aefc80ed5b4af9d3ff844748859d7a2298b116b49"
]
],
"content": "📅 Original date posted:2015-06-25\n📝 Original message:On 6/24/2015 8:00 PM, Raystonn wrote:\n\u003e\n\u003e \u003e Consensus-code changes are unanimous. They must be.\n\u003e\n\u003e Excellent. Now we are getting to some actual written rules. How about \n\u003e updating the BIP process documentation with this? Everyone should be \n\u003e able to read the rules of the coin they are buying.\n\u003e\n\u003e One moment though. Can you tell me how this particular rule came to \n\u003e be? The creator of Bitcoin violated this rule many times. So it must \n\u003e have been adopted after his departure. What process was followed to \n\u003e adopt this new rule? Was there consensus for it at the time? A huge \n\u003e portion of the user community is under the impression that Satoshi's \n\u003e written plans, some of which violate this new rule, will be \n\u003e implemented. So there certainly would not be consensus for this rule \n\u003e today.\n\u003e\n\nGreat question; very fair. I, for one, eagerly await Mark's answer.\n\nI hope nobody forgot to tell adversaries totally outside the open source \necosystem what the rules for hard forking changes are.\n\nThe Chinese miners have it right - we have to work together. If you \nwant to see who's trying, look at who has written a concrete BIP/code \nvs. who hasn't; who has made changes in response to feedback, and who \nhasn't.",
"sig": "d7a26fca96e9ac5822424c311e7fc20da60ed6bd92453ff8b24d676aab34c8b2dfc4ad71bc4d449feb8814b36c31430fc2c07fb7db7b1b0f4d7cc9a6849b3a93"
}