what's the bullshit? why not focus on the proposal instead of making it about someone?
Discussion
The entire LukeCoin narrative is bullshit.
i could be wrong but to me it comes down to being for or against arbitrary data... personally i lean towards fuck arbitrary data
Can you explain how to differentiate a hash or public key from arbitrary data?
you dont have to, there isn't many financially viable ways to store blob data on bitcoin.
cost doesn't deter art NFT enthusiasts and it never did. the higher cost can actually make it more enticing
idk you are talking based on what. inscriptions become popular because they cost less. and they are possible because core removed script size limit policy on witness for tapscripts. ignoring all the warnings.
inscription txs cost less than a dolar.
also even without the history its really simple to understand: cost always gonna make it less.
there are not many places you can sneak data into a tx.
nobody is gonna create thousands of txs just for an image constantly.
i understand that's the counter argument
realistically how can the new soft fork proposal can be used to censor monetary transactions?
The issue of course is that you cannot stop arbitrary data and op_return was put in place to provide a printable place to put arbitrary data vs having it pollute the utxo set. Locking down the system to remove all vectors of injecting data would remove nearly all functionality of Bitcoin beyond the most basic uses and doom the scalability of the system. It will be freedom money for the few and relegate it to the same fate of the gold standard if it even makes it that far.
The best way to make sure bitcoin is used as money and not arbitrary data is to use it as money.
don't remove all vectors just the weakest ones
remove all capacity to pollute UTXO set
(i have no idea what I'm talking about)
That's what core is doing.
You can’t remove all vectors to pollute the utxo set without removing all the functionality that makes level 2 scaling possible. That’s the point of having a garbage can like feature in the form of op_return.
what that looks like in practice is Bcash
no Segwit, larger blocks
"bcash" is a prejorative adam back and greg maxwell invented when they were seething about it on reddit. you're not supposed to call it that when you're not going out of your way to belittle it
BSV?
BSV is the retarded stepson of the blocksize discussion
From what I've seen they have solved the scaling issue without changing the protocol (version 1 of the whitepaper)
its easy to scale when you have zero usage
