Synchronizing a node has cost me 4 days, of these 4 days 50% has been taken by the last year.
Terabytes of data read on an ssd...if the bullshit inscriptions continue, in 10 years no one will be able to sync a Bitcoin node at home.
As you can see, it is not feasible to increase the block size, nor is it feasible to allow crappy inscriptions in the chain.
Some of you are either dumb or have never run a node and give hypocritical opinions.
Some of us still believe in decentralization.
With bip158 you get privacy without having to run a full Bitcoin node.
You can run your node without inscriptions and Runes and whatnot with Bitcoin knots π€·πΌββοΈ
No, you still validate the whole block and all transactions are added to your hard disk, the only thing you do is not to add those transactions to your mempool. The computational cost is negligible.
I've been living in a false simulation the whole time π
But what if many run Bitcoin knots instead of Bitcoin core. Let's say the majority wouldn't the spam gradually disappear from the mempool.
For me the unnecessary data (inscriptions, ...) is an attack on decentralization.
nostr:nprofile1qqs0m40g76hqmwqhhc9hrk3qfxxpsp5k3k9xgk24nsjf7v305u6xffcppemhxue69uhkummn9ekx7mp00qjrgs can explain this much better than me.
Exactly, but unfortunately the miners are interested in bullshit spam.
So what's the solution? Even if we lower the block size, these morons will continue burning cash to push their scams.
Doesn't doggie coin perform better with this stuff?
I have no idea wtf you are talking about.
You asked what the solution was so I was saying I'm pretty sure changes in the doge or Litecoin fork helped
Those are shitcoin forks with barely any activity on them compared to bitcoin, which makes them completely irrelevant.
What crack are you smoking that makes you keep forgetting the conversation like this? You fucking asked what can be done about the difficulty of dealing with heavy amounts of blockchain data, you didn't fucking ask what blockchain has the most traffic, now you're bitching at me because you can't remember what's relevant to your own question and acting like that's my fault after I already fucking held your hand through it? People you love are going to die not being able to get medical procedures you can't afford to get them because you're as fucking stupid as them. Go bother someone else
I run 3 nodes. 2 full, (1 knots, 1 core) and a pruned node. I have taken to Locally updating the timechain on a separate storage device every quarter as a much quicker data loader.
Although I wish the Pruned node was utilized for more software.
Dude, I used to wait for weeks to download a music album, and you are saying 4 days is too long to secure your stack? In 10 years people will still be able to run nodes without problem, not to mention there are people working on alternative core implementations that sync faster.
As far as I understand, the 4 Mb block size will in the future always be fully utilized with whatever is humanly possible on BTC. It's futile to argue moralistically here. Ordinals, runes, NFTs ... whatever humans find useful will be inscribed on that block space. Precisely because it's the most secure and trusted chain/network in the world.
I'd say, it's better to focus on making data transfer speeds faster and ssd space cheaper over time to match the growing demand of BTC block space, so that node decentralization remains high.
in the near future the whole world will be on Starlink high-internet speeds. I don't see this as a major issue, the #Bitcoin marketplace is open to anyone for any purpose the protocol rule allow. Therefore, let people waste Sats on blockspace if that's what they want to do, they will be outbid in the future as more participants use the timechain.
β‘β‘β‘β‘β‘β€οΈβ€οΈβ€οΈβ€οΈπππ
If you found the experience difficult, imagine what your computer had to go through π
I remember the Bitcoin core team was working on a fast synchronization mechanism based on using bip157/158. I remember they tested it and the partially synchronized node was ready in minutes.
I don't know what happened after that or why it was never meeged.
1. SSDs are so cheap nowadays.
2. The price per GB will continue to decrease.
3. There are ways to speedup the initial sync.
4. Four days is not that long anyways for something that you only have to do once.
5. You can run a pruned node.
6. Only shitcoiners are into Inscriptions/Ordinals, let them waste their sats.
Up until now, I haven't cared much one way or the other with regard to inscriptions - I know almost nothing about how they work. Not being able to sync a node in 10 years would be a good reason to start caring, though.
What is it about inscriptions that take so much time to sync. I think I know enough to know it's not purely due to the size of the data: the last 2 years combined account for less than 30% of the total blockchain. (roughly 15% for each of the last 2 years). So, what is it about processing inscriptions that turns 15% of the data into taking 50% of the total time to process?
PS. I'm not sure what terabytes of data you are referring to... all the sources I can find suggest the total blockchain size is still more like 620 GB. Perhaps this suggests why I'm misunderstanding something.
Mining with nostr:nprofile1qqsq9k04vahllseell55m74n3047y88pzlr0z5yany32st29fapqmgsppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctc87ckyu pool gives you freedoom of choice on data inclusion in mined blocks. This also helps decentralization of mining.
If syncing via network becomes too slow, one could resort to ordering/sending/receiving an SSD with a blockchain that's a few days/weeks old via mail?
Exporting the blockchain to another SSD from a running node should be fast/easy.
So only a few GBs would be left to load via network.
You can do this already without mailing anything, I believe lukedashjr has a website that offers a snapshot to go from.
The issue is mostly disk IO. An NVMe drive will significantly improve sync time. These days, $/tb is the same for NVMe and SATA SSDs so it is only a matter of choosing a node that supports NVMe drives. That will bring your full chain sync to 24-36 hours.
Demurrage Fixes this
Storage Rent is the only viable option for fixing chain bloat
either dumb or have never run a node, true, I would add a third, they know what they are doing and have bad intentions.
It's quite annoying. I think I remember Ocean working on a way to filter these transactions out of blocks they add to the blockchain, but they're just one player. I'm still trying to learn more about the mining side of things. Maybe some day I'll try to give that a whirl, but not until I understand things more.
Dont forget to take morris law into account. 10 years from now, you will not have the same storage capacity that you have now.
Also, synchronizing it not a problem I think. Who cares if it takes 4days or 4weeks..
+ If the increasing weight of the blockchain surpasses the increasing storage capacity of a regular ssd, you can always run a pruned node.
The present moment is all we have, itβs all anyone has, we can strive for change yes, but adaptation is of utmost importance.
Did you consider the freaking increase in technological developpement in the last few year?
Computing power will catch up
πππ
