đź”” đź”” NEW OP_RETURN đź”” đź”” Who the fuck is the absolutely out-of-control god-complex-bearer idiot currently moderating the Core github discussion? Can somebody in that cabal of self-appointed politicians find a less *****ed handler for the discussion about spam attacks?
đź”” đź”” NEW OP_RETURN đź”” đź”” "Filters work" "but here's an example of a filter not preventing spam getting in a block" cc portlandhodl, peter todd, rob ham, Lopp, sjors, wuille and every other Einstein in Bitcoin Core making that argument we know you aren't actually that stupid:
đź”” đź”” NEW OP_RETURN đź”” đź”” Someone pushing for a major change to Bitcoin is affiliated with a company whose current exploit of Bitcoin was the motivation for the change.
đź”” đź”” NEW OP_RETURN đź”” đź”” Spam is quite delicious. I don't understand the controversy.
đź”” đź”” NEW OP_RETURN đź”” đź”” @benthecarman is a gay but we forgive him
🔔 🔔 NEW OP_RETURN 🔔 🔔 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.
đź”” đź”” NEW OP_RETURN đź”” đź”” TRUC is an abuse of policy to try to provide security, which unlike spam filters, will never be safe; and implementing this actually distracts from real solutions for Lightning. Anchors bloat the chain and UTXO set merely to avoid a little extra work in the wallet, and attempt to give an unwarranted discount to such abuse. Cluster mempool appears to have little purpose to justify its excessive complexity. "Packages" are just a lazy way to avoid figuring relationships out automatically.
🔔 🔔 NEW OP_RETURN 🔔 🔔 Haha …. poop…..
đź”” đź”” NEW OP_RETURN đź”” đź”” Since the restrictions on the usage of OP_RETURN outputs encourage harmful practices while being ineffective in deterring unwanted usage, i propose to drop them. I suggest to start by lifting the restriction on the size of the scriptPubKey for OP_RETURN outputs, as a first minimal step to stop encouraging harmful behaviour, and to then proceed to lift the restriction on the number of OP_RETURN outputs per transactions
đź”” đź”” NEW OP_RETURN đź”” đź”” Unfortunately, as near as I can tell there is no sensible way to prevent people from storing arbitrary data in witnesses without incentivizing even worse behavior and/or breaking legitimate use cases. If we ban "useless data" then it would be easy for would-be data storers to instead embed their data inside "useful" data such as dummy signatures or public keys. Doing so would incur a ~2x cost to them, but if 2x is enough to disincentivize storage, then there's no need to have this discussion because they will be forced to stop due to fee market competition anyway. (And if not, it means there is little demand for Bitcoin blockspace, so what's the problem with paying miners to fill it with data that validators don't even need to perform real computation on?). But if we were to ban "useful" data, for example, saying that a witness can't have more than 20 signatures in it, then we are into the same problem we had pre-Taproot: that it is effectively impossible construct signing policies in a general and composeable way, because any software that does so will need to account for multiple independent limits. We deliberately replaced such limits with "you need to pay 50 weight for each signature" to makes this sort of analysis tractable. There's a reasonable argument that this sort of data is toxic to the network, since even though "the market is willing to bear" the price of scarce blockspace, if people were storing NFTs and other crap on the chain, then the Bitcoin fee market would become entangled with random pump & dump markets, undermining legitimate use cases and potentially preventing new technology like LN from gaining a strong foothold. But from a technical point of view, I don't see any principled way to stop this. - apoelstra -michaelscott -cbspears