pull down to refresh
But I am absolutely for attacking NFTs on Bitcoin at the social level and given solutions that would actually work, the technical level.
For example, if your gripe is that we should have block size less than 4MB, reduce block size, if your idea is to make a present day tx size, be capable of benefitting 10 or more users (thereby reducing tx cost and thereby more easily outcompeting with spam on the fee market) look into solutions that enable coinpools. I personally like playing with ideas that help people "wait" on their transaction longer in a way where the user doesn't feel like they're waiting somehow. The actual "how to do this" is a bit up in the air right now, but its something of active interest to me.
reply
For the record since you inadvertently pinged me by linking a post where I shared a link, BIP-110 is at best pointless. However, it targeting op_if is what changed my opinion from sleeping through this argument to being actively against it.
https://knotslies.com/
This person demonstrates how to find a transaction they made where they made a hex encoded tiff file and embedded it into their transaction without using any of the methods BIP-110 is targeting. I suspect a ready and easy to use tool capable of this will be launched on BIP-110 activation day out of spite.
Additionally, the constant use of "but you have to be technical to do that so I don't care about the concern" from being able to use op_if, to being able to embed a hex encoded tiff image in a transaction is very frustrating. We can make it easy, easily.