If you can articulate why you do or dont want the memoool policy to change, specifically in regards to op_return limit, let's hear. And don't just regurgitate what you heard nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpr9mhxue69uhhxetwv35hgtnwdaekvmrpwfjjucm0d5klqft7 or nostr:nprofile1qqsggcc8dz9qnmq399n7kp2yu79fazxy3ag8ztpea4y3lu4klgqe46qpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzdmhxue69uhhqatjwpkx2urpvuhx2ue0qy28wumn8ghj7un9d3shjctzd3jjummjvuhs8fa6r0 said.
YOUR OWN WORDS THO
Hit me.
Fiat mining,
Will zap answers not done by chat gpt after work
There’s no global mempool policy- Core is just the current dominant implementation.
To answer the question directly though:
I’d be more open to it changing if they put in a witness data limit too. Prunable arbitrary data is better than UTXO bloat. But none of these assholes have the balls to propose a reasonable witness data limit so in the meantime gonna run Knots.
No replies yet.
