Damus
Luke Dashjr profile picture
Luke Dashjr
@Luke Dashjr
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.
3729❤️57🤙61❤️4🔥3🚀32
idsera · 121w
Hope together with this fix, we allow Drivechains, so people can explore new kind of sidechains.
AJ Nobody ⚡🏴 · 121w
Thank you for your service. You and others continue to build the cathedral, while others spray paint graffiti as if it's something to be proud of. And honest BIPs suffer from the unintended consequences of recent activations.
Cyber Seagull · 121w
If the purpose was to allow more functionality, and it did, isn't this a personal opinion ? Demand is not a bug or spam. It's one thing to opt in to Knots, it's another for core to continue to decide changes like this. This and Future changes that exclude large segments of use that otherwise foll...
RealJohnDoe · 121w
👍👏🧡😊
nobody · 121w
Hey nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk this is the first I've heard of it. Thanks for putting this out there. Is Bitcoin Knots a drop in replacement for core or do I need to build a different config and redownload the chain?
vnprc · 121w
How did you fix it?
Meridian · 121w
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 sim...
nostrich · 121w
What's the best way some one with software experience xan help you move the forward? Bitcoin Core Pr reviews and testing?
ew0k · 121w
Knot gonna make it
Protect Your Keys · 121w
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
Anonostr · 121w
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
⚡₿it₿y₿it⚡ · 121w
nostr:nevent1qqsfcrfn7qcckejr4up7q6fqqumjv3zj82y6xvsyvq74f8d6eepugmcpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qyg8l9eqjxx0sz7yxs7nrmcey3shfltpl9tg4u0tzrc45yf6u4ju7e5psgqqqqqqslslvgz
SmokingEarl · 121w
this is great work
Alex · 121w
and it's not one of the notable changes? https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-25.1.md
𝕾𝖊𝖗 𝕾𝖑𝖊𝖊𝖕𝖞 · 121w
Hey Luke! Sent you an invite to the 24hr frog talk!! Check DMs 🐸
tdub · 121w
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?
Gravital organics enthusiast · 121w
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.