<unnamed>

Public Key

npub19k7ufmdc4tt0xpk65r2uv3t26nw6e22vjqe4fj4r907ewf8v3t4svw2466

Profile Code

nprofile1qqszm0wyaku244hnqmd2p4wxg44dfhdv49xfqv65e23jhlvhynkg46cpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsqs7amnwvaz7tmwdaehgu3wd4hk6qguwaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skcqgewaehxw309aex2mrp0yhxsmmyd33x7ctjvshx7un8qyghwumn8ghj7umpw3ekzem99eu8j7s6n49n4

Publishing to

relay.damus.io

nos.lol

nostr.mom

nostr.bitcoiner.social

relay.hodlboard.org

satsage.xyz

Last Notes

2026-08-11 08:07:09 CEST

- reply

I don't think Adam's opinion on this makes much sense at all. I think he's also one of the people that fell for the "filters are censorship" argument.
It's already been shown (and you can check yourself by running the filters) that as you say the difference in fee estimation was overall marginal (at least for the kind of filters we are talking about currently), same for relay (read AJtown data for example. The effect was just marginal at best).
Not only that, but both the above problems have more effective and far more elegant solutions than forcing the entire decentralized network to run with the same mempool policies/filter (probably one of the most retarded things to attempt ever).
Bitcoin core still uses many filters (because, spoiler, they work as a disincentive if widely adopted) and added new policies BTW (like TRUC). And no, it's not incoherent to call it your mempool since it's literally your mempool.
Unfortunately, the bip110 retardation has discredited all the good rational discussion around filters.