Is the OP_RETURN limit removal a BIP?
No — this specific change was not formalized as a BIP.
Instead, it was implemented as a mempool policy change within the Bitcoin Core software, meaning it doesn’t alter consensus rules (i.e., the rules all full nodes must follow to stay in agreement about what Bitcoin is). It only changes how Bitcoin Core nodes handle and relay unconfirmed transactions, which is part of policy, not consensus.
➡️ Because it’s not a consensus change, it doesn’t require a BIP.
BIPs are generally reserved for:
New consensus rules (e.g. SegWit, Taproot)
Network-wide upgrades
Major standardizations or protocols (e.g. BIP32 for HD wallets)
---
🔍 So what is this, then?
This change is a policy-level update merged into the Bitcoin Core codebase:
Specifically, it lifts the 80-byte limit on OP_RETURN data in the mempool.
Nodes running this updated software will now accept and relay larger OP_RETURN transactions, up to a much higher limit (potentially blocksize-dependent).
This will go live in Bitcoin Core v30, expected October 2025.
---
👀 Why does that matter?
No BIP = No global consensus required.
So if you run a non-Core client (like Knots, or custom builds), you’re free to reject or filter those transactions. That’s what Knots users are doing.
This is why Bitcoin Knots is rising in adoption — it's preserving stricter filters to protect against what its supporters call “spam” or “non-monetary bloat.”
#studybitcoin #pow
nostr:nevent1qqs04sah5jtngawwz8ak9z25l2z2lnycet8xwr5tm8ffwe6h89xkjycpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygp022celc2q3a57ur5snmv0etqn330nwrq9mcj0pkphptd8jafryvpsgqqqqqqsfvqmxy