Nostr Web Client

To fork or not to fork seems to be on some minds tody regarding #BitcoinCore.

Now I'm not even a tech amateur so I have no clue what the ramifications are. I just don't want #Bitcoin to get screwed up!

If people want to store files on the blockchain, I should think that that's what shitcoins are for. Store your file on the XRP blockchain, for instance and then "attach" (I don't know how this could be done, but I presume the same relative manner in which one "attaches" a file of some type) your XRP file to some amount of Satoshi, and there you are.

Maybe I'm wrong, but that seems (conceptually) to be the answer.

Reply to this note

Please Login to reply.

Discussion

M0053 8mo ago

Ironically you are actually making both sides of the argument here.

One potential reason for removing the op_return limit is so data can be added to the blockchain in the least obtrusive way. Anchor data, or the hash of a file for example. (Related to what you're suggesting) And op_return is the best place to do this. Currently spammers are just jamming data into the witness area which is objectively worse.

On the other hand enabling unbounded data in transactions is arguably not what bitcoin is for.

And there is much nuance in the arguments as you dive in really...

Thus the drama.