📅 Original date posted:2015-06-18
📝 Original message:"And I never had a problem with Bitcoin-XT while it was just a
patch-set with no consensus changes. But a controversial hard fork of
the chain is something else completely."
How is that different? The only difference is in who makes the fork
and if that group has a chance of actually splitting/overriding the
network. So Mike and Gavin are using the trust and relationship they
have garnered through Bitcoin for their purposes (malicious or not).
There are only 20-30 people with the same kind of recognition who
would be able to do that. M&G already wanted to make a fork in 2014
for entirely different reasons (http://pastebin.com/3kt5Reeh).
On Thu, Jun 18, 2015 at 2:50 PM, Wladimir J. van der Laan
<laanwj at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On Thu, Jun 18, 2015 at 02:29:42PM +0200, Pieter Wuille wrote:
>> On Thu, Jun 18, 2015 at 1:14 PM, Wladimir J. van der Laan <laanwj at gmail.com>
>> wrote:
>>
>> > Like in any open source project there is lots of decision making ability
>> > for code changes. I'd say look at the changelog for e.g. 0.11
>> > https://github.com/bitcoin/bitcoin/blob/0.11/doc/release-notes.md#0110-change-log,
>> > or follow pull requests for a while, to see how many decisions about
>> > changes are made from day to day. No, I'm not sitting on my hands, and so
>> > is none of the other contributors that you'd like to get rid of.
>> >
>>
>> The analogy goes further even. Even though I disagree with some of the
>> changes you're making, I respect Mike's (and anyone's) right to make a fork
>> of Bitcoin Core. That's how open source works: if people disagree with
>> changes made or not made, they can maintain their own version. However:
>
> Sure. According to github, there exist 4890 forks of the bitcoin/bitcoin repository.
>
> Forking the code is perfectly fine in itself, that doesn't even need to be said, it's how open source works. Make your changes, run your own version, contribute back the changes (or not).
>
> And I never had a problem with Bitcoin-XT while it was just a patch-set with no consensus changes. But a controversial hard fork of the chain is something else completely.
>
> Wladimir
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBCgAGBQJVgr5LAAoJEHSBCwEjRsmm5mMH/0yLGGQQefRVdmM/nJZ60b/z
> iTCUUzY4eLL67FRC6pqGA18RdUt4Etl4wEqvgXH/B9mWIAM2yQD/jnxutYrEIoBT
> 8Jyd1OhmmKF8MN5/uE7JNPivIuHs0ioF+qTxlbdElpVZ2NodVotznbTvuqJgXUFb
> c9Et5L5n7g55uPzDt+MSV5iBDJaMiBAnZA00aTLGmYmNXxcy7xBwCFX3dDij8krv
> 0+zdpNNAKm85k1rG2jHCM+0onu+TOIur03pPd5OZktgr18P6UvAQ6A59yAkGgFai
> 4l6VVNJ40g3PzItGQ7wsKZ8s/qG5LlcEppxMlG6CX1dIDpxbrwx2aJmeNjwSLKQ=
> =LbA3
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Benjamin [ARCHIVE] /
npub17k…sr5tq
2023-06-07 15:38:28
in reply to nevent1q…xwqs
Author Public Key
npub17kz55p7ysz4ftvq2xyr2zamc776cygwcm5fdz8ndj3jm5umm65xq4sr5tqPublished at
2023-06-07 15:38:28Event JSON
{
"id": "b38381c0ac378b2a141bb9bf768d242c5ff81e0158ff8f9238984f87f6a01951",
"pubkey": "f5854a07c480aa95b00a3106a17778f7b58221d8dd12d11e6d9465ba737bd50c",
"created_at": 1686152308,
"kind": 1,
"tags": [
[
"e",
"23c1bb2f25b9e7356b48aa2a86751c4f26fb3977b440917a1cb3512c200b0b2f",
"",
"root"
],
[
"e",
"82bcb564d05b497fc8e0da128ee3b4633fad1b3b30707b12f053338d8dcbd3ad",
"",
"reply"
],
[
"p",
"5c0b7fca51fd4830b4d9f840de063faebeeabd3bb5dd118de9cdf50a6feaaf98"
]
],
"content": "📅 Original date posted:2015-06-18\n📝 Original message:\"And I never had a problem with Bitcoin-XT while it was just a\npatch-set with no consensus changes. But a controversial hard fork of\nthe chain is something else completely.\"\n\nHow is that different? The only difference is in who makes the fork\nand if that group has a chance of actually splitting/overriding the\nnetwork. So Mike and Gavin are using the trust and relationship they\nhave garnered through Bitcoin for their purposes (malicious or not).\nThere are only 20-30 people with the same kind of recognition who\nwould be able to do that. M\u0026G already wanted to make a fork in 2014\nfor entirely different reasons (http://pastebin.com/3kt5Reeh).\n\nOn Thu, Jun 18, 2015 at 2:50 PM, Wladimir J. van der Laan\n\u003claanwj at gmail.com\u003e wrote:\n\u003e -----BEGIN PGP SIGNED MESSAGE-----\n\u003e Hash: SHA512\n\u003e\n\u003e On Thu, Jun 18, 2015 at 02:29:42PM +0200, Pieter Wuille wrote:\n\u003e\u003e On Thu, Jun 18, 2015 at 1:14 PM, Wladimir J. van der Laan \u003claanwj at gmail.com\u003e\n\u003e\u003e wrote:\n\u003e\u003e\n\u003e\u003e \u003e Like in any open source project there is lots of decision making ability\n\u003e\u003e \u003e for code changes. I'd say look at the changelog for e.g. 0.11\n\u003e\u003e \u003e https://github.com/bitcoin/bitcoin/blob/0.11/doc/release-notes.md#0110-change-log,\n\u003e\u003e \u003e or follow pull requests for a while, to see how many decisions about\n\u003e\u003e \u003e changes are made from day to day. No, I'm not sitting on my hands, and so\n\u003e\u003e \u003e is none of the other contributors that you'd like to get rid of.\n\u003e\u003e \u003e\n\u003e\u003e\n\u003e\u003e The analogy goes further even. Even though I disagree with some of the\n\u003e\u003e changes you're making, I respect Mike's (and anyone's) right to make a fork\n\u003e\u003e of Bitcoin Core. That's how open source works: if people disagree with\n\u003e\u003e changes made or not made, they can maintain their own version. However:\n\u003e\n\u003e Sure. According to github, there exist 4890 forks of the bitcoin/bitcoin repository.\n\u003e\n\u003e Forking the code is perfectly fine in itself, that doesn't even need to be said, it's how open source works. Make your changes, run your own version, contribute back the changes (or not).\n\u003e\n\u003e And I never had a problem with Bitcoin-XT while it was just a patch-set with no consensus changes. But a controversial hard fork of the chain is something else completely.\n\u003e\n\u003e Wladimir\n\u003e -----BEGIN PGP SIGNATURE-----\n\u003e Version: GnuPG v1\n\u003e\n\u003e iQEcBAEBCgAGBQJVgr5LAAoJEHSBCwEjRsmm5mMH/0yLGGQQefRVdmM/nJZ60b/z\n\u003e iTCUUzY4eLL67FRC6pqGA18RdUt4Etl4wEqvgXH/B9mWIAM2yQD/jnxutYrEIoBT\n\u003e 8Jyd1OhmmKF8MN5/uE7JNPivIuHs0ioF+qTxlbdElpVZ2NodVotznbTvuqJgXUFb\n\u003e c9Et5L5n7g55uPzDt+MSV5iBDJaMiBAnZA00aTLGmYmNXxcy7xBwCFX3dDij8krv\n\u003e 0+zdpNNAKm85k1rG2jHCM+0onu+TOIur03pPd5OZktgr18P6UvAQ6A59yAkGgFai\n\u003e 4l6VVNJ40g3PzItGQ7wsKZ8s/qG5LlcEppxMlG6CX1dIDpxbrwx2aJmeNjwSLKQ=\n\u003e =LbA3\n\u003e -----END PGP SIGNATURE-----\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development",
"sig": "b8ad94540676f06dac683365ebd7b58931985c8b1fbdc434aea1b265f197d8f840653c65b0a6f13e20153cf01004a5887f9efa1a36c243d4091c7aecacf9ea50"
}