nostr:nprofile1qyxhwumn8ghj7cnjvghxjme0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyr7at68k4cxms9a7pdca5gzf3svqd95d3fj9j4vuyj0nyta8x3j2whad7ya nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3uamnwvaz7tmwdaehgu3dwp6kytnhv4kxcmmjv3jhytnwv46z7qpqwnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqcjfkft nostr:nprofile1qy8hwumn8ghj7mn2w4khqtndv5hszythwden5te0dehhxarj9ekxzmny9uqzpprrqa5g5z0vzy5k06c9gnnc485gcj84qufv88k5j8ljkmaqrxhgkgzyc0 first of all I support your work and truly hope noderunners win the spam war.
I do have a question. What is your view on an OP_RETURN relay limit default of datacarriersize=46 in Knots bitcoin.conf and also Ocean? That would support privacy transactions while still blocking spam and inscriptions by default.
Obviously there is a much bigger debate going on, so perhaps this is seen as low priority. But it could increase support for Knots over Core from the supporters of privacy transactions.