pull down to refresh
metaprotocol is WAY better outcome, imo, than storing image data in the UTXOs
it's also a lot easier to point to and say: "look at this UTXO on the mempool browser, you're paying somebody to embed json... which isn't art, even if the JSON contains a pointer to some image file made by an artist, stored on some server somewhere"
The image file, the 'ordinal theory' is the metaprotocol. None of this stuff exists, either it's baseless speculation on data you don't "own" or it's an attack neither of which bip-110 fundamentally fixes.
That's why I do not support it.
in the case of these problematic UTXOs, it's not the metaprotocol that's the problem. meta protocol is (as you've suggested) just JSON formatting, indicating what kind of message we're looking at.
the issue of the "spam" is not the JSON. it's that there's a bunch of data embedded in witness, which is part of the UTXO and needs to stay in RAM in order to validate incoming blocks. since the UTXO is unspent validation requires that the node keeps track of this information. that is what's filling up the RAM of the computers operating validating nodes.
I was under the impression... that witness script in op_if op_endif was unreachable, in other words the computer just ignored large blocks of op_if of_endif freeing up resources.
Large inscriptions... make large blocks easier to verify rather than harder. No?
Why would any of these people... want these NFTs? They are infinitely reproducible.
And if "we" actually did Bip-110... we would be increasing NFT scarcity not decreasing it. Just "put" that sucker (to the extent than an NFT even exists) on a Satscard or an opendime...
And then you can physically sell or transfer it to anyone you want, it becomes even 'more' rare at least for a short while... because no more "can be made".
It would arguably give the Bitcoin-NFT market even more legs and actually make large inscriptions provably scarce. They become one-of-a-kind sort of... which is the opposite to the message we want to convey.
Not to get off topic... but knots/bip-110 does nothing to slow the growth of memecoins, 83 bytes is large enough for almost any metaprotocol. That's why IMO bip-110 misses the forrest for the trees.