Replies (29)

Thanks for bringing some sanity back into this debate Jimmy. 160 was probably the right default. I think it remains to be seen though if this change adds more spam. This “new” vector is 4x the cost and I think inscriptions allow the full blocksize to be used, so up to 40x the storage of op_return. The market for arbitrary data is partly a function of low fee rates combined with the novelty/rarity of the embedded data. I don’t think it’s possible to permanently address either, but it seems like higher fees will lead to decreased interest in spamming the chain, so let’s figure out ways to get the fees up
BitcoinIsFuture's avatar
BitcoinIsFuture 3 months ago
Meet Core V31, it can start showing pictures, playing sounds and vids because core devs state that "Bitcoin is not just Money, it can be EVERYTHING".
Why have that junk on their so nations that hate it already, start messing with on ramps/off ramps and use it as an excuse……. That is unnecessary…….
You're thinking about this rationally from a free market perspective. But do you think a state would ever seed compromising "data" and not care about paying 4x? Then people "hosting" that data on their nodes could be held liable, de-incentivizing node runneing and leading to more centralization and control I haven't followed this discussion closely so if anyone has an answer to that I'm all ears
Just because the software doesn't have a built in image viewer, doesn't absolve anyone legally or morally from distributing it. An FTP or HTTP server don't display images either. They just distribute it. It's unnecessary, illegal, wrong, and most of all disgusting.
Let's solve mining centralization by solo mining, mining to smaller pools and DATUM. People will still use inscriptions, since they're cheaper anyway. So it doesn't actually do anything to solve mining centralization. It just allows things to be added anonymously that miners wouldn't allow for legal and moral reasons. Just look at BSV. Why does Core want to turn Bitcoin into BSV?! We already fought an entire war against this.
I followed this discussion a lot, and I resonate with your impression of it namely: core devs are looking at it from a purely technical angle + economic incentive angle, but they are not considering AT ALLthe possibility of a malicious actor who only cares about hurting the network (and does not care about using more expensive ways to achieve this). It almost fee like this "we already won and so we can do whatever" mentality has spread a bit too much....I'm worried about this arrogance/over-confidence, and lack of being cautious
Chris's avatar
Chris 3 months ago
Death by 1000 cuts… The direction Core and many bitcoiners took is worriesome 😔
100%. Pride (and lack of humility) tends to come before the fall- so I am the most bearish on Bitcoin since I bought my first sats Feels like the same incremental destruction of liberty that the government uses to control people and outcomes (not a perfect analogy but same vibe) Segwit, taproot, now op return.. It’s just.. Don’t worry…pats head condescendingly The devs know what they’re doing.. Spam is already getting through.. Trust the science.. I’m a retard when it comes to technical details but I am good at pattern recognition, so my nonchalant “Bitcoin don’t care” attitude is quickly shifting
we are on the same page man, agree with everything you said. I'm also bearish here, but on the other hand, if we want to look at the bright side, this whole debate was very useful to stop core "monopoly" as the only reference implementation and the push-back from the community has been great (it shows that we still have enough plebs who are vigilant and do not take shit) Let's see how things unfold, gotta stay positive and vigilant though, also because ain't no other basket where we can put our hope in! 🤟
tbh, I'd go for a 160 default, but this malicious actor stuff is all just FUD. It's possible today with inscriptions *and* OP_RETURN via libreRelay and a willing miner. Packing crap in the witness data has been possible for the past 4 years. What are they waiting for? "contiguous bytes", which this change makes slightly easier to do? That's the only thing stopping them?!
Bro, let me show you few notes. I will post them one after another. Core devs blocked Mechanic and other people only for mentioning Citrea during the initial Github discussion on OP_RETURN increase.
BitcoinIsFuture's avatar BitcoinIsFuture
Fuck Citrea and Fuck Chainway lab shitcoiners. 🤡🤡🤡 "With Citrea, Chainway is working to help Bitcoin better accommodate decentralized finance (DeFi), NFTs and other use cases that were previously only possible on smart contract-based blockchains like Ethereum, but are now possible for Bitcoin to handle." "We're hearing things like Citrea is better than Ethereum," Chainway Labs co-founder Orkun Mahir Kılıç told CoinDesk. "It'll be better with time, because there's like $1 trillion, as of now, sitting in the Bitcoin blockchain. It is the most secure, battle-tested and decentralized blockchain. And we are bringing decentralized finance to it." 🤡🤡🤡 https://www.coinglass.com/news/91227 Same technology on ZBT/ "ZEROBASE is a decentralized cryptographic infrastructure network that enables verifiable off-chain computation using zero-knowledge proofs (ZKPs) and trusted execution environments (TEEs). It powers products like zkStaking, zkLogin, and ProofYield—bridging institutional DeFi, user privacy, and real-world asset strategies. ZEROBASE delivers programmable, compliance-aligned staking and transparent cryptographic assurance without exposing sensitive data." image Core V30 is malware that enables Citrea shitcoin technology. Majority of Core devs are compromised.
View quoted note →
Hello Jimmy, Why dont you review the title of Satoshi's White paper? "Bitcoin: A Peer-to-Peer Electronic Cash System" Satoshi Nakamoto You and your other "MalDevs" seem to have forgotten.
Didn't they tell you that filter don't work? Well see the current OP_RETRUN filter limiting data to less than 83 Bytes. image
BitcoinIsFuture's avatar BitcoinIsFuture
Let’s do a quick thought experiment. Imagine a government wants to attack Bitcoin. What could they do? They can compromised a number of developers. The developers could start slowly degrading Bitcoin. They could change the definition of Bitcoin being "digital currency that uses peer-to-peer technology" to just be a "peer-to-peer network". They could change the definition of the datacarriersize. Using that as argument they could deny fixing the inscriptions spam. Then they could use the inscriptions spam as an argument that spam is unstoppable so they better blow up OP_RETURN and invite even more spam. Just like BSV did after which someone uploaded CSAM to the BSV blockchain. View quoted note →
View quoted note →