Oddbean new post about login | logout So it’s a valid transaction! And why should we do something against valid transaction? Why is somebody right about how to use bitcoin and somebody is wrong? I don’t like Luke’s ideology against inscriptions. Im fine when he “fixed” it in Knots, but why should we “fix” it in Core? Let people decide, give them both implementations and see which wins
Most of the decisions that go into “what is a valid transaction” are based around data size, spam prevention, and performance. If we make it easier to spam then thats not a feature it’s a bug.
For me it’s not spam. It’s a valid use case within the current rules of bitcoin. Not to forget that I get more sats from mining. Bitcoin has already a spam protection. It’s called transaction fee. No one can “spam” Bitcoin forever because it costs a lot of money and the outcome is zero.
you are assuming that inscriptions are a feature, not a bug. devs are simply fixing bugs. there was a bug in 2010 that allowed the creation of 184 billion btc. that txn at the time was considered a valid txn but again, this was a bug in the software so devs went ahead and fixed it. just because you can fit 20 people in a car that seats 5 doesn’t mean you should. you can go ahead, but i’d rather not.
Because that was against bitcoins socal contract which says there will never be more than 21 Million Bitcoin. What is the social contract about inscriptions? That’s why we are discussing the topic.
So, Whirlpool and Paynym is also a bug? https://x.com/Diverter_NoKYC/status/1732337726924448102
This 👌🏼👌🏼👏🏼👏🏼 They want to censor free markets.. 🤣🤣🤣 Good luck to them 🤣🤣
This argument again and again... The 2010 bug with 93 billion BTC was also valid...
That was a hard bug because it was against the social consensus rules of bitcoin. Today the case is different, because we don’t have a consensus that bitcoin transactions should not used for inscriptions. Changing the limits will change exactly nothing. Most miners are profit oriented and they would extremely stupid to change bitcoin in a way they get a smaller reward. What really happens with such an update is a soft network split. Your node no longer accepts and forwards inscriptions, but others will. This means your mempool differs from others. This can lead to problems when it comes to calculating transaction fees. Because your node doesn’t see all the high fee transactions miners see.
I let you see it in real time, the fees are rarely staggered. https://orangepill.ovh
It’s nearly a 10 BTC difference but okay 👌🏻 Feel free to censor transactions because you don’t like how people use bitcoin my node will never do so
Spyware is valid software and we normally use antimalware to protect ourselves from them.
So Samurai Whirlpool and Paynym is also spam? https://x.com/Diverter_NoKYC/status/1732337726924448102
This is allowed by default on bitcoin-core and fits within the acceptable usage since it’s a standard transaction. Luke further tweaking it so that it’s not standard on his pool is a personal choice, if you don’t like it then direct hashpower elsewhere. This is a separate issue from the one described in my post.