pull down to refresh

Full quote: "The big blockers are back already and trying a round two. This time apparently with Bitcoin Core in support."
What did he mean by this?
The only reason to run a full node is if you are interacting with the base chain.
If a single interaction with the base chain costs more than setting up and running a full node for a year or two, then you don't really gain any decentralization benefit from keeping the current block size limit.
If/when base chain fees pass that threshold, increasing the block size, moving to side chains, or some other transaction scaling method will be inevitable.
reply
If a single interaction with the base chain costs more than setting up and running a full node for a year or two
Actual interesting debate point.. I think anyone who calls it the "war" is already sensationally discrediting themselves. The intensity of the fork situation is only experienced by those who dox themselves for fiat on social media (and I guess by those who actually have to implement code on exchanges). Everyone else can actually chill, they don't even need an opinion, just run a node if you care. "War" is a CIA psyop.
reply
If a single interaction with the base chain costs more than setting up and running a full node for a year or two, then you don't really gain any decentralization benefit from keeping the current block size limit.
Excellent point! This would be a great metric to chart over time. tx vs full node opex.
Expanding block size would also increase full node opex while reducing tx cost (in theory). The wrinkle is that the lower tx cost may invite increased ordinals and inscriptions. The induced demand theory we see with highway expansion. Traffic only gets reduced temporarily as more cars fill up the space leading to the same or worse traffic congestion.
reply
This is a valid point, and one that doesn't get discussed enough.
reply
200 sats \ 0 replies \ @BITC0IN 4 Apr
If you haven't been paying attention, you probably should be.
Core fucked up. They are shirking their historical mandate to fix exploits, while having opened the door in the first place to said exploit.
Not confidence inspiring. Especially for any future "upgrades".
reply
I'm conservative when it comes to the one and only shot we have at a fair decentralized currency. I'd like to not have to worry about Bitcoin for decades. Call it ossification but I'm with Carvalho when he says Taproot opened up a lot more potential than what's been explored thus far. I'm against any further soft forks for a few years at least.
When it comes to how the blockchain is used, I trust fees as the transaction gatekeeper more than anything else. That being said feel free to run what you want on your node.
reply
That's right. Let's not turn Bitcoin into a biochemical research lab like Ethereum.
reply
I'd like to not have to worry about Bitcoin for decades.
The same. So from decades perspective two things should be addressed:
  • quantum computing
  • lack of free market between active (transacting) and passive (holding) Bitcoin users (by naturally reached equilibrium of annual inflation level between both of them)
15 sats \ 0 replies \ @xz 3 Apr
I don't think ossification and improvement are mutually exclusive.
A better way to pose the dilemma IMO,
ossification camp = ain't broke, don't fix we change btc protocol camp = ain't broke, fix anyway
ossification and change. ossification is like evolution. Sometimes there are very minute changes in organisms. It's not always adaptation.
reply
Are you familiar with the Blocksize Wars?
The short version is, back in 2017 a large number of bitcoiners thought bitcoin wasn't going to be able to continue to scale because of the "small" number of transactions that can fit into a block, which can only be mined about every 10 minutes...
The problem is, increasing the blocksize decreases overall security. There was a massive clash in the bitcoin community about this, leading to a hard fork, which became Bitcoin Cash...
Apparently some people are being vocal about wanting a larger blocksize again, but we already know how that plays out - Bitcoin Cash failed.
If you're interested in getting the full history, I'd highly recommend this book. Really great info in here on how changes are made to the protocol. https://www.amazon.com/Blocksize-War-controls-Bitcoins-protocol/dp/B08YQMC2WM
reply
I am familiar and I read it. I don't understand who in Bitcoin Core supports big blocks though.
reply
with big blocks I take it it's now proven that they take longer to propagate, so you'd potentially have miners spending more time mining on top of 'stale' blocks, which reduces hash power securing the network, so miners are incentivized to be close together on the network?
anyway, lukewarm jr has lost a lot of credibility over the past year.
reply
It’s not the size of the block that matters, it’s what you do with it…. 😏
Hash rate refers to how many hashes you can produce per second. It’s a measure of total power needed to solve for the hash of a block.
Once a miner solves the hash, they get to add the next block.
Blocksize essentially refers to the number of transactions you can fit into a block. That can be done rather instantly, it doesn’t really take any extra time to fill a 1 MB block vs a 2 MB block. It does take extra computational power to go through and validate the transactions, but not to solve for the hash itself. Shouldn’t affect hash power.
Some people think we should have large blocks so the network can scale by handling more transactions… the problem is, that weakens the security of the network. It allows for a greater DoS impact, it makes mining a little harder for individuals, it’ll make nodes require significantly more storage, and all of that pushes the network towards centralization.
Only thing you really need to know, though, is that it this failed in the past.
If you want to know more about how this stuff works, start at the 99bitcoins channel to make sure you have a solid understanding of mining, and then read the Blocksize Wars by Jonathan Bier.
reply
i dont own any bitcoin cash but how exactly did bitcoin cash fail?
Ossification is a dead end and would just kill Bitcoin.
Is this statement an obvious fact?
In nature, there are many examples where little to no change occurred in hundreds of millions of years: Sharks, horse-shoe crabs, cockroaches, etc. They reached "evolution perfection" or to put in a less flattering perspective: They have reached genetic Ossification. That is, they found a place where change is simply not required because it just works. I recognize that these species named have an inherent selection bias because they are the ones that survived. Countless other creatures that could not adapt perished.
I know the idea of ossification in software development is considered a dead end. And for apps, this is largely true. However, when we talk of Internet protocols that are crucial for its survival: DNS, SMTP, BGP and others, serious care should be considered before any change is implemented.
Few people are saying, "let's tinker with DNS to improve it", and there are fewer cases where such changes get implemented. But they do happen after very careful and considered review. And they happen very quickly when survival is at stake (major security breaches e.g.). DNS works so well that we seldom think about it. Bitcoin is not an app. We should study and follow the trajectory of change management that other crucial Internet protocols have undergone. If a change were made to DNS with unforeseen catastrophic consequences, the Internet could shut down. If a change were made to Bitcoin with unforeseen catastrophic consequences, the Internet of Money™ would shut down. Perhaps that is the very reason why we don't "tinker and make changes" to crucial Internet protocols.
reply
31 sats \ 3 replies \ @om 4 Apr
Few people are saying, "let's tinker with DNS to improve it",
Proposed DNS killers started with Namecoin that dates back to the times of Satoshi and continue to this day.
and there are fewer cases where such changes get implemented.
ENS, Unstoppable Domains and DIDs got some traction. There is still an ongoing debate whether DNS over HTTPS is worth turning on, the question being whether you want to give your data to your local provider or to some global spy company like Cloudflare.
DNS works so well that we seldom think about it.
DNS is a privacy nightmare and and an attack vector for deplatforming (see attempts to deny Gab a domain name by GoDaddy). The whole public key infrastructure is a dystopian hell, see Belarus and Kazakhstan mandating installation of government-issued certificates and EU's attempt to legislate the same.
reply
Proposed DNS killers started with Namecoin that dates back to the times of Satoshi and continue to this day.
For a protocol that governs just about every routable packet on the Internet and has remained stable and functional for decades it's remarkable how few core changes there have been. Compatibility with IPv6 was a notable one.
DNS is a privacy nightmare
So is Bitcoin. Just ask Chainalysis.
Does that mean we fork DNS to be better at privacy? Does that mean we fork Bitcoin to behave like Monero? No. That is what layer 2s are for: use Tor to keep Cloudflare on their toes, and there are some zero knowledge methods out there keeping Chainalysis in R&D mode.
reply
45 sats \ 1 reply \ @om 4 Apr
it's remarkable how few core changes there have been
Because it's heavily regulated, not because it's perfect.
Does that mean we fork Bitcoin to behave like Monero?
Well, such a thing exists, it's Monero (not strictly a fork, whatever). It lost to Bitcoin due to many factors, most importantly inherently horrible SPV wallets, no scalability solution, and no covenants at all (which delayed atomic swaps 10 years or so). But it wasn't obvious from the start that this was a bad idea, and some Moneroids appear here for whom it's still not obvious.
use Tor to keep Cloudflare on their toes
I am in fact doing just that right now. However, many sites, especially Cloudflare ones, don't work under Tor. It's an ongoing war.
reply
However, many sites, especially Cloudflare ones, don't work under Tor. It's an ongoing war.
I hear you. It's like the Great Firewall of China run by a corporation. I think Cloudflare routes 30+ % of the Internet now? Yet another deeply concerning centralization of power.
reply
I dunno guy, but between somebody running a full node for me because it's impossible to run one at home and somebody holding my keys for me because it's impossible to pay miner fees, I'd rather have someone run a node.
It's been 7 years, the necessities of the market are not the same as they used to be, our internet is a lot better, block propagation over clearnet is a lot faster, we have things as, SPV, ZK-Proof and assumeUTXO.
It might really be time to get those bigger blocks rolling, the mempool is telling us that it needs bigger blocks.
P.S: Call me "big blocker" or "shitcoiner" all you want, the technical reality of Bitcoin is completely independent or your philosophical opinion and mine, you all will need to prune your 1TB external SSD connected to a raspi 4 in next 2 years anyways.
reply
Lol were we not kind enough to let big blockers have two shots at failure, just give it a test already, you can bring back the big blocker debate in 20 years
reply
There's a group of some of the most active Core devs who are heavily against any spam filtering, shut down any discussion about filters, and close PRs which seek to fix the spam problem.
We're seeing the attack vector play out IMO. It's always been the case that if you can capture 5 or 6 key people, you can influence the direction of Bitcoin development.
I don't know if any Core devs have been captured as such, but the culture has certainly changed (by their own admission) from one which patches exploits, to one which panders to miner earnings above all other considerations (again, by their own admission).
I think this is dangerous, and I would like to see other node implementations which give the user control over the transactions they want to propagate in the mempool gaining more market share, such as Knots.
Further, I hope more and more miners point their hashing to Ocean Mining, which gives individual miners the option to select their preferred "block template", with the option to not include any of the transactions which take advantage of the spam exploits in the block.
The bigger picture is that the developments above would add to Bitcoin's decentralisation, reduce attack vectors, and give individual users more sovereignty over their participation in the network.
reply
Hopefully Luke is going to go fix Ethereum to get all the big blockers focused on bad ideas over there. Solana seems to be attracting a lot of shitcoiners.
reply
I actually feel very conflicted about this.
Naturally I think there's tendency for the community to be against major change. why change when it runs and risking the long term price action we have.
And miners who are now investing millions for future profit would be growing risk averse.
And how many of us actually understand the full scope of the changes.
Imo I think Bitcoin is in a bit of stalemate. It's now too big to implement some changes. It should have taken a lot more risk when it's smaller.
I feel too many are worshipping Satoshi as the gospel, but he's not perfect and there were things that were fixed.
reply
From the context in the thread it appears that Luke thinks being against gimping script to fight ordinals is to be equated with being a big blocker.