There's only two charts in bitcoin that matter, and price isn't one. The first is the hashrate and the second is the number of @BTC Map merchants - @Nathan Day at @TokyoBitcoinBase
OrangeSurf
_@orange.surf
npub18h0w...ws8m
There's been lots of debate about Core v30 removing the OP_RETURN size/count policy defaults, so I ran the numbers for the latest mempool research report: 
There were three big waves of OP_RETURN usage: 2019, 2024, 2025. Nearly all standard transactions. The nonstandard ones are so rare you can hardly see them on the chart.
The 2019 Veriblock wave actually put more data on-chain than anything since. People talk about recent OP_RETURN usage like it's unprecedented, but surprisingly it isn't.
The important thing is that the spikes in nonstandard OP_RETURNs were in Mar 2024, May 2025, Aug 2025. All before v30 shipped in November 2025. The rate hasn't gone up since. At all. In fact it's come down
Runes transactions were standard under the old rules and would even still be standard for #BIP110 (the proposal that's supposedly aims to curb data embedding). If these guys are serious about stopping data they should block runes.
TL;DR: v30 recognised what was already occasionally happening on-chain. Nonstandard OP_RETURNs are vanishingly rare, haven't increased post-v30, and the current wave is already cooling off. The data doesn't support the panic.
Read the full report linked below 👇
mempool research
OP_RETURN Report
A data driven analysis of OP_RETURN usage on bitcoin, revealing that the overwhelming majority of OP_RETURNs are standard, nonstandard usage has no...
The 2019 Veriblock wave actually put more data on-chain than anything since. People talk about recent OP_RETURN usage like it's unprecedented, but surprisingly it isn't.
The important thing is that the spikes in nonstandard OP_RETURNs were in Mar 2024, May 2025, Aug 2025. All before v30 shipped in November 2025. The rate hasn't gone up since. At all. In fact it's come down
Runes transactions were standard under the old rules and would even still be standard for #BIP110 (the proposal that's supposedly aims to curb data embedding). If these guys are serious about stopping data they should block runes.
TL;DR: v30 recognised what was already occasionally happening on-chain. Nonstandard OP_RETURNs are vanishingly rare, haven't increased post-v30, and the current wave is already cooling off. The data doesn't support the panic.
Read the full report linked below 👇
mempool research
OP_RETURN Report
A data driven analysis of OP_RETURN usage on bitcoin, revealing that the overwhelming majority of OP_RETURNs are standard, nonstandard usage has no...
As signing device developers begin to add support for BIP322 it would be great to have on-device message viewing. I've sketched out an idea of how this could be done with QR & vis SD.
Gist
BIP322_for_Signing_Devices.md
GitHub Gist: instantly share code, notes, and snippets.
Sparrow just added address chunking which is really nice, I've made an extension to experiment with this on mempool, try it out and let me know if you have any feedback
📂 Get Extension Here:
GitHub
GitHub - orangesurf/mempool-chunker
Contribute to orangesurf/mempool-chunker development by creating an account on GitHub.