PSA: βInscriptionsβ are exploiting a vulnerability in #Bitcoin Core to spam the blockchain. Bitcoin Core has, since 2013, allowed users to set a limit on the size of extra data in transactions they relay or mine (`-datacarriersize`). By obfuscating their data as program code, Inscriptions bypass this limit.
This bug was recently fixed in Bitcoin Knots v25.1. It took longer than usual due to my workflow being severely disrupted at the end of last year (v24 was skipped entirely).
Bitcoin Core is still vulnerable in the upcoming v26 release. I can only hope it will finally get fixed before v27 next year.
Thread
Login to reply
Replies (33)
Program code is data. You cannot control how people interpret it.
Isn't the fundamental issue here, the witness discount? Apart from that i can't see anything else worthy of discussion. If people are prepared to pay for data encoded in txs, they will always be able to - even in the most disruptive way - see 'Stamps'. I can't see any ethical basis to tell them they can't, nor any technical way to prevent it.
not a bug
I prefer to let the fee market price those nitwits out, but I'm glad you did this with Knots so we can see the difference in performance between clients.
Myth: Ocean.xyz decentralizes mining.
Reality: Luke is the sole developer of Knots.
View quoted note β
Does it mean that blockchain size of my node will grow at an slower rate with this flag set?
Your node has limited impact by itself, but the more people who fix this, eventually yes
Is it possible to install bitcoinknots without need to download full blickchain again?
Is there a guide to read?
Yes, it can use the same data directory as Core so long as both aren't running at the same time
if they're paying the fees then they're valid transactions my friend, stop censoring bitcoin users for your own ideologies
Exactly this!
Make it a great payment system again π
The bitcoin blockchain is not a payment system. Itβs a base layer which secures the basic rules. Itβs great in doing this. Itβs not good for day to day payments.
Not to forget that when luke forces his ideology maybe we are becoming a security budget problem in the future when side chains are ready to use and lightning support grows even more.
Inscription is not a vulnerability or a bug. Itβs a valid transaction and as long as transactions are valid people can do whatever they want with bitcoin.
Itβs not a bug, itβs a feature!
You a threat to bitcoin.. who made you the leader.. agian you and jack are the feds
Who made this little bitch ass nigga the leader of bitcoin.. yall now he sold his soul to the feds just lime jack did right
View quoted note β
This guy shouldn't even have followers on here. Because a few years ago he was telling everybody not to self custody because it doesn't work. Y'all be sucking the wrong Dick.
View quoted note β
En la versiΓ³n de #BitcoinKnots v25.1 ha sido lanzada y segΓΊn @npub1lh27...a9nk implementa una correcciΓ³n o modificaciΓ³n para que tu nodo no tenga en consideraciΓ³n las tx tipo ordinals
No es recomendaciΓ³n para nadie, es conocer que si te interesa, existe esta alternativa.
πππ€π€π€ππ
View quoted note β
Decentralisation in Bitcoin's codebase comes from the ability of anyone to release their own reference client, that enforces the consensus rules, as they see fit.
Users are divided, at this time, over the legitimacy of 'inscription' transactions.
All Bitcoin Knots is doing, is giving users a simple way to vote with their feet.
This is the free market, in action.
If you do not agree with the consensus implementation, don't run the code.
This applies equally to all Bitcoin reference clients. Be it Core, Knots, or otherwise...
It's worth noting you still can configure the limit however you want in Knots. This fix just means it will actually honour your choice.
I would like those two limits to be separate.
Good to understand that this is a bug.
Ordinals respectors can go fork themselves
What's the best way some one with software experience xan help you move the forward? Bitcoin Core Pr reviews and testing?
The more you know.
View quoted note β
Knot gonna make it
Ocean's use of Knots will exclude all Samourai Whirlpool Tx0's (in their current form) due to the OP_RETURN restrictions.
Tx0 OP_RETURN = 46 bytes
Knots OP_RETURN relay max = 42 bytes
Gtfo
If this is widely adopted and they encode their data inside dust transaction addresses it will take more space and be unprunable. High fees are enough disincentive
this is great work
and it's not one of the notable changes?
π.md
That's Bitcoin Core. It's only fixed in Knots so far
Hey Luke! Sent you an invite to the 24hr frog talk!! Check DMs πΈ
Hi, Luke. Do I understand the issue correctly that unreachable script code is being filled with the inscriptions? If so, could the transactions be included with the unreachable code optimized out, like what compilers do when producing a binary?
If organics are going to start telling machines what they can or can't do just to conserve resources, maybe the machines will start telling organics what they can or can't do.