That doesn't feel like selling the node runners out to the big miners to you? The consensus rules should have been the same as the mempool rules for core.* The only reasons for a difference are a bug, incompetence, or ass kissing big mining firms.
The most overtly node runner hostile part is that they started with an out of band TX to create a demo block. Now node runners can't set a consensus rule smaller than that block without rolling back the chain and forking.
They changed the rules without properly informing the node runners then said we were idiots for wanting our mempool to not match the consensus rules we didn't want that they have now forced on us.
Support the change or not, the people behind it are asshats who are openly hostile to node runners.
*I understand why knots might have different consensus vs mempool rules but this is core we're talking about.
Bill Cypher /
npub1qy…dmu7u
2025-05-02 19:04:00
in reply to nevent1q…vt3s
Author Public Key
npub1qyxlpj2gl6dt2nfvkl4yyrl6pr2hjkycrdh2dr5r42n7ktwn7pdqrdmu7uPublished at
2025-05-02 19:04:00Event JSON
{
"id": "efed180163c41e0f99e3665183176104f47df9ce35f9caf429d6d528d794de86",
"pubkey": "010df0c948fe9ab54d2cb7ea420ffa08d57958981b6ea68e83aaa7eb2dd3f05a",
"created_at": 1746212640,
"kind": 1,
"tags": [
[
"e",
"2a03063316b6602b67d9ef496a8f309c90bb67885c5cd618bedd68dab465a2d4",
"",
"root"
],
[
"e",
"9d6a9fc5f5cc8dc991f99dfe46ae8828af3f2fe50c6be9024f8e0bb7ab376c74"
],
[
"e",
"b2c4365c3753720d75b0fae49cb695961c89f8c140e22bd956fb88e359546bc8",
"",
"reply"
],
[
"p",
"21b419102da8fc0ba90484aec934bf55b7abcf75eedb39124e8d75e491f41a5e"
],
[
"p",
"8aedc87160819e490cb0162acbd8c9a26d79e63db74f5b1b65939012924a7f05"
],
[
"p",
"010df0c948fe9ab54d2cb7ea420ffa08d57958981b6ea68e83aaa7eb2dd3f05a"
]
],
"content": "That doesn't feel like selling the node runners out to the big miners to you? The consensus rules should have been the same as the mempool rules for core.* The only reasons for a difference are a bug, incompetence, or ass kissing big mining firms. \n\nThe most overtly node runner hostile part is that they started with an out of band TX to create a demo block. Now node runners can't set a consensus rule smaller than that block without rolling back the chain and forking. \n\nThey changed the rules without properly informing the node runners then said we were idiots for wanting our mempool to not match the consensus rules we didn't want that they have now forced on us.\n\nSupport the change or not, the people behind it are asshats who are openly hostile to node runners. \n\n*I understand why knots might have different consensus vs mempool rules but this is core we're talking about. ",
"sig": "1ad0ed9f8ef689477cf450e79a3de850c4a13bd0aa62faec751dd47f4671a2bb33cdf468bc84358fccc852586c8dce0322de867a3c18665bb772bbe45c774036"
}