1/8
In the next Bitcoin Core release, the OP_RETURN size limit will be removed.

Previously, you could only fit 80 bytes - basically just a hash or a small tag.
Soon this restriction will be gone. https://t.co/SEyZ1qDyl8

2/8
OP_RETURN is like a pocket in a transaction. You can store data there that doesn’t affect the balance but can be used by applications.

L2s and protocols use it to interact with Bitcoin: pass signals, store hashes, confirm actions.

If Bitcoin becomes more open to data,
Rooch can use that immediately.

6/8
Rooch is ready for this kind of change.

MoveVM can already process and use incoming data from Bitcoin.

No need to rewrite the whole system.
Just adjust what’s written into the transaction.

7/8
Some devs worry about more junk hitting their nodes via OP_RETURN. Others are excited because you can now do airdrops or pass contract structures without awkward hacks.

Infrastructure is slowly shifting from just secure to also convenient.

8/8
Around Bitcoin, there’s a growing space where you can build apps without breaking consensus, but still using it as a foundation.

Changes like this strengthen the position of L2s we often talk about. They use Bitcoin not just as an asset, but as a source of data and trust.

3/8
Before, everything hit the limit. Just one short message at best.

Now apps will be able to pass more information directly, without workarounds. More space means more flexibility.

4/8
For Bitcoin-based protocols, this means a bit less pain.

For developers, it’s much easier to launch things that used to feel impossible.

So overall, It’s a step toward broader accessibility.

5/8
What about @RoochNetwork ?

Their MoveVM handles execution.
Bitcoin acts as the security layer.