The best thing about knots is that it's NOT part of the Bitcoin Core project, at least in terms of governance, while sharing much of the same code, especially consensus related. This is important for people who are unhappy with the direction core is moving and have no other way of expressing themselves besides running a different implementation.
Murch raises some concerns about the "unilateral" nature of knots, being modified and maintained, by a single dev (in contrast to core's 40 regular contributors) which makes this PR especially reckless. The person who made the PR (Todd) is telling unhappy node runners to "just run knots" on stage at bitcoin++ while defending on behalf of Core the op_return change he has been a proponent of for some time, and which was met with similar resistance the last time he proposed it. This is in a real sense an endorsement by Core, at least of Knots as a viable alternative. Meanwhile, another core dev Murch, is ringing alarm bells about Knots as a project with "a single developer pushing directly to master without peer review." A project node runners are being told to use by the PR author if they don't like it? Something stinks. This PR should be withdrawn immediately.
jgbtc /
npub1s9…23ctl
2025-05-15 12:53:52
in reply to nevent1q…av0d
Author Public Key
npub1s9vv8ztavpupdevkrlsvr28fhur6f4c6amxwa4umu7hsq74jxqusp23ctlPublished at
2025-05-15 12:53:52Event JSON
{
"id": "6118ad57f50b9aece6fbf91a8f38dd0e59f74eb22c27bd96b746cc06b55ff417",
"pubkey": "8158c3897d607816e5961fe0c1a8e9bf07a4d71aeecceed79be7af007ab23039",
"created_at": 1747313632,
"kind": 1,
"tags": [
[
"p",
"1989034e56b8f606c724f45a12ce84a11841621aaf7182a1f6564380b9c4276b"
],
[
"p",
"426c37d185741a0fcfb74d04dbdee38d6125faeeaf69fa1aaa69172e8002a943"
],
[
"p",
"b8851a06dfd79d48fc325234a15e9a46a32a0982a823b54cdf82514b9b120ba1"
],
[
"p",
"83e818dfbeccea56b0f551576b3fd39a7a50e1d8159343500368fa085ccd964b"
],
[
"p",
"6a359852238dc902aed19fbbf6a055f9abf21c1ca8915d1c4e27f50df2f290d9"
],
[
"p",
"50d94fc2d8580c682b071a542f8b1e31a200b0508bab95a33bef0855df281d63"
],
[
"p",
"4ca484914ae2434465594011d448c073849b7b1570b17171cc967572dbec3b96"
],
[
"p",
"be41636e3e6d2fe99e065200dc8a9034f9128064fdcd39b75a6983cae55c4909"
],
[
"p",
"82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2"
],
[
"p",
"3731e169d0b3816f4a4a9ac84c66aa423d4f4ea0f78b56a1df90609b85be0885",
"wss://nostr.einundzwanzig.space"
],
[
"e",
"14e3687a002692a6a2b93549d5cc0a2713546403523d8396a24a7c638e4c5f88",
"wss://nostr.einundzwanzig.space",
"root",
"3731e169d0b3816f4a4a9ac84c66aa423d4f4ea0f78b56a1df90609b85be0885"
]
],
"content": "The best thing about knots is that it's NOT part of the Bitcoin Core project, at least in terms of governance, while sharing much of the same code, especially consensus related. This is important for people who are unhappy with the direction core is moving and have no other way of expressing themselves besides running a different implementation.\n\nMurch raises some concerns about the \"unilateral\" nature of knots, being modified and maintained, by a single dev (in contrast to core's 40 regular contributors) which makes this PR especially reckless. The person who made the PR (Todd) is telling unhappy node runners to \"just run knots\" on stage at bitcoin++ while defending on behalf of Core the op_return change he has been a proponent of for some time, and which was met with similar resistance the last time he proposed it. This is in a real sense an endorsement by Core, at least of Knots as a viable alternative. Meanwhile, another core dev Murch, is ringing alarm bells about Knots as a project with \"a single developer pushing directly to master without peer review.\" A project node runners are being told to use by the PR author if they don't like it? Something stinks. This PR should be withdrawn immediately.",
"sig": "2db87958c6b5a9cafa08d96ed7fa5bb326829fe5fbabc38df1dcfc5b7f89dc73a97ebf8c0f805c885e7f46d4aab254b229b4522d5ec1d0ce0e74983f5c85ca68"
}