I believe Ordinals can solve it in the same way. An ipfs hash is only 32 bytes. It fits perfectly fine in a 40 byte OP_RETURN.
No need to panic about it, just store the meat somewhere else and keep using the blockchain for what it was meant for -- validation.
By the way, nostr:npub16v2dg43sg34m3r2tuw60zqv3t2a59pdr7mqq6vw4qg2wwsdljw0s4fenz8 is this true? Or is it just that OP_RETURN 80 byte is required for your system to work?
Just to be clear, I am merely stating the obvious: it is orders of magnitude easier to implement a second layer solution for blockchain data storage.
No idea what is wrong with everyone nowadays.
nostr:note18ka3ezt782au8x6tg84x33xtd4svakrcntdgd6u0hq2yrfsshzfsp5wtql
