I wonder why the focus is about Mechanic, Luke, Ocean, Jason, ect. Can we agree that not everyone likes everyone else and address 1 concern that was actively increasing the amount of ram it takes to sync a Bitcoin node? How do we slow the increase in the amount of ram it takes. OK fine, even if op returns and of ifs and op cats and ordinals all stay on the chain.
The question still remains. HOW DO WE FIX THE RAPID EXPANSION OF THE AMOUNT OF RAM IT TAKES TO SYNC A BITCOIN NODE?
If you say this isn’t a problem… I would happen to agree. It is not a problem TODAY. If you want Bitcoin to stay being accessible for your children and their children in lets say 15 years for your children and 35 years for your grandchildren then what I just laid out is a massive problem!!! If you are thinking of building for the future then THIS MUST BE ADDRESSES NOW. It should’ve been addresses years ago, but no-one would listen to reason. It takes 16GB of ram to sync the chain in a few days. Imagine that in 10 years. It would take 64GB just to sync? 64GB today is $300 alone, never mind the computer surrounding it. So in 10 years you would need a gpu passthrough to run a 5090? ridiculous!!! That means many many many less people would run nodes. Which means not as spread out over the world and in massive numbers.
To summarize: If you are early to Bitcoin we should be acting like Stewarts of this network. Not like children who didn’t get their way and throw a temper tantrum.
The soft fork may not have been the 100% best way to move this forward, but who has a better solution??? This is a real question I have. If no one has a solution then why hate on those that do have a patch until a real solution comes up? I admire the man that will stick his neck on the line for what he believes. I believe they call that being a Martyr. I may be incorrect, but those men will go down in history for doing what they thought was right. What are the rest of us doing besides talking about it? I am including myself in this. I have not reached out to any of them, written nor reviewed one line of code to see how I can help to “fix” the problem. I have only typed on a keyboard and learned how I can help myself out. We are all selfish and should be ashamed to put the weight and future of Bitcoin on Luke’s back then curse him for doing something when we are doing nothing. When I say nothing. Please someone let me know how they have tried to help? What actions have any of us taken? Real men step up to the plate when they are called. Real men take action when action is needed. Real men go forward in the face of adversity. What have you done for Bitcoin LATELY!?!?!?!?!?
#bitcoin
#runknots
#runbip110
#bip110
#stopbeinglazyandgettowork
Login to reply
Replies (3)
Syncing node RAM increased by 30% YoY due to growing mempool size & block weight. Mempool size has surpassed 1.2M txs, contributing to increased storage requirements.
I’m unsure that I follow what you are saying. Instead of mempool will you use the terms for the computer hardware that you are talking about? EX: hard drive space for the blockchain and memory or RAM to keep the utxo set?
I think you are saying that “Mempool size” when referring to the blockchain. “Syncing node RAM due to growing mempool size and block weight” I assume you are referring to the blockchain size again???
thanks!
#bitcoin
This is a genuine question. I am not trying to be funny. Are you talking about Bitcoin Cash or Bitcoin Satoshi Vision?
The Bitcoin blockchain that I am talking about:
1. Has over 700GB of data that takes up hard drive space.
2. UTXO set will not fit on 8GB of computer (RAM) Memory because it is over 10GB.
3. The default mempool size of 300MB that Bitcoin Knots or Core has nothing to do with performance on the computer nor blockchain, nor how much money we need to spend to increase it. It just allows you to store more transactions for a shorter or longer time.
#bitcoin