pull down to refresh

Bitcoin Core has a mempool policy limit on the size of extra data in transactions but inscriptions found a way to bypass it

The bypass is the bug

If your node is relaying transactions that bypass the limits you intended for it then it's not working properly

You are incorrect.

Bitcoin Core has allowed extra data in transactions deliberately for many years. This tool of mine does exactly that to publish text, and was created prior to even segwit, let alone taproot: https://github.com/petertodd/python-bitcoinlib/blob/master/examples/publish-text.py

reply
Bitcoin Core has allowed extra data in transactions deliberately for many years

Sounds like a mistake I'd like to fix

reply

If you want to "fix" that you should at least propose a technical solution that isn't just a dumb cat-and-mouse game.

reply

But I don't have a technical solution

I can state my opposition and my reasons for it but persuasion is about all I can try to do right now because I don't know if it's even possible to fix it technically

reply