They are not irrelevant to most of the people I see arguing about the issue who consistently have one or more of those facts wrong. I didn't write that for you, I wrote it for the community at large.
I can set a limit on my mempool size. Mempool is RAM only, the least constrained resource on any node I've seen. Mempool is transient and constantly changing. Mempool is far less important than what gets validated in a block to go on chain and be on my hard drive for all eternity. If spam is in op_return instead of witness data I gain the option to not store that spam on my hard drive for all eternity.
Unless you plan to stop validating those blocks and hard fork you accomplish nothing but making your own view of pending transactions less accurate by filtering your mempool. You also remove options from yourself for not storing monkey jpgs because they get put into witness data you can't eliminate without losing economic information your way.
You picked a side, good for you. You picked the wrong side for your stated goal of limiting spam stored on your node. You hold an inconsistent position. You must now change your position, change your goal, or concede to being irrational. If you really think mempool is more important than on chain I can't help you.
Bill Cypher /
npub1qy…dmu7u
2025-05-09 14:39:51
in reply to nevent1q…hcpf
Author Public Key
npub1qyxlpj2gl6dt2nfvkl4yyrl6pr2hjkycrdh2dr5r42n7ktwn7pdqrdmu7uPublished at
2025-05-09 14:39:51Event JSON
{
"id": "79e3537b723bc536695c2f7a663dfde32d79fb8c01b598ba5781168169a575e4",
"pubkey": "010df0c948fe9ab54d2cb7ea420ffa08d57958981b6ea68e83aaa7eb2dd3f05a",
"created_at": 1746801591,
"kind": 1,
"tags": [
[
"e",
"be29ee027753d5b6530b7dc4ed641323ccafb0768d1080d2980a31515bebe51c",
"",
"root"
],
[
"e",
"8848389bb47b8376379c3421bdc7ce09819e9614fc8291cdb53675f9cec52440"
],
[
"e",
"5ce1fb590cad629bab9f182aec3e67c3e59bfc4bbc8c94886bc6df70b2bc65dd",
"",
"reply"
],
[
"p",
"010df0c948fe9ab54d2cb7ea420ffa08d57958981b6ea68e83aaa7eb2dd3f05a"
],
[
"p",
"dd1f9d502c7951df47e8f8ed245e8bfa24f7e82c28f19399a8f0e74b06113a21"
]
],
"content": "They are not irrelevant to most of the people I see arguing about the issue who consistently have one or more of those facts wrong. I didn't write that for you, I wrote it for the community at large.\n\nI can set a limit on my mempool size. Mempool is RAM only, the least constrained resource on any node I've seen. Mempool is transient and constantly changing. Mempool is far less important than what gets validated in a block to go on chain and be on my hard drive for all eternity. If spam is in op_return instead of witness data I gain the option to not store that spam on my hard drive for all eternity. \n\nUnless you plan to stop validating those blocks and hard fork you accomplish nothing but making your own view of pending transactions less accurate by filtering your mempool. You also remove options from yourself for not storing monkey jpgs because they get put into witness data you can't eliminate without losing economic information your way. \n\nYou picked a side, good for you. You picked the wrong side for your stated goal of limiting spam stored on your node. You hold an inconsistent position. You must now change your position, change your goal, or concede to being irrational. If you really think mempool is more important than on chain I can't help you. ",
"sig": "d15969b0adf2c2e5b61fc9b90057fe5810e13941d83838aa1bcd7ff302e5d5c768971c10e96bf3c7211b2fa21062b1852e0266af0642e3c067398d7ce2190b2d"
}