Bitcoin Core P2P Implementation BLOWS

[sledgesickle]

Your "community" complains that Bitcoin needs help. That you need more nodes. More participation. WELL. How do you expect even people like me who believe in the basic premise of community BANKING to participate when THE SOFTWARE implementation is SO PROBLEMATIC that anyone with a RATIONAL MIND will GIVE UP on the whole idea. HUH? HUH? I have more than adequate computer resources to establish a NODE. The resource I'm lacking is AVAILABLE PEERS. Bitcoin Core needs to be INFINITELY MORE AGGRESSIVE at seeking out other PEERS. Or alternatively, new nodes need to be able to download a VERIFIED CHAIN of sufficient HEIGHT. PERIOD, END OF STORY. Requiring the new nodes DO ALL THE WORK, just to get started IS.... sorry, I have no other polite words to use... STUPID. I am an extremely patient individual. And as write this, I can assure you that I will persist, as a lamb, BAH, BAH, BAH... to complete the SYNCHRONIZATION process... maybe because I'M JUST BORED TO TEARS. The "pandemic" makes strange bedfellows. BUT I DIGRESS.

I was TEASED initially with the prospect of completing SYNCHRONIZATION in as little as 35 hours at around the 10% complete progress point. But as I've recently conquered 30%, left to it's own devices (figuratively) Bitcoin Core creeps to 4-12-16 weeks until completion without my continuous manual ADDNODE activity on the console. This works quite well by the way. I can coax up some serious progress using the Bitnode website, INSTANTLY generating substantial progress by selecting potential target nodes... BUT I NO LONGER SEE THE POINT. For sure, my residential VERIZION FIOS connection fails me miserably. But I doubt my provider is any different than any other. My node simply DISSAPPEARS from time to time. Thanks to the Bitnode crew for allowing me to "ping" myself. I find myself wishing that I'd set up a Tor network early on, figuring that ANY sort of "tunneling" device would improve network response. But at this point, I don't want to sit through yet another "processing blocks" wait time. Come on people. Who cares anyway. Bitcoin is no longer the currency of the people...

PLEASE REFRAIN FROM COMMENTS THAT ATTEMPT TO EDUCATE ME ON ALL THE BS YOU THINK I HAVEN'T TRIED YET.

In fact, I would be perfectly happy if the moderator blocked all comments to this post. OR EVEN DELETED IT. I'm sure somebody will read it. Hopefully someone who might want to actually do some engineering WORK, yes, I do mean WORK, to SAVE BITCOIN from this pathetic demise. But you know? I REALLY DON'T GIVE A RATS ASS.

[1713943645]

1713943645

[1713943645]

1713943645

[1713943645]

1713943645

[xcaret]

are you finished your snivvelling or is there more to come ?

[pooya87]

The resource I'm lacking is AVAILABLE PEERS. Bitcoin Core needs to be INFINITELY MORE AGGRESSIVE at seeking out other PEERS.

I have never had any issues finding or connecting to peers either through bitcoin core or my own code. There are more than sufficient number of peers and core finds them well enough.

Or alternatively, new nodes need to be able to download a VERIFIED CHAIN of sufficient HEIGHT.

If you don't like running a full node the solution is not this, the real solution is for you to use an SPV client instead.
Bitcoin is based on the "verify, don't trust" principle and that can not change.

I was TEASED initially with the prospect of completing SYNCHRONIZATION in as little as 35 hours at around the 10% complete progress point.

I have more than adequate computer resources to establish a NODE

That means you don't have "more than adequate" resources. The time to fully sync bitcoin core with an adequate PC and an adequate internet speed is 5 hours, when it takes you 7 times more just to get to 10% it means there is a problem in your end.

I can coax up some serious progress using the Bitnode website, INSTANTLY generating substantial progress by selecting potential target nodes

that's an interesting claim since to my experience most of the nodes listed in this site, specially the first couple of pages are spy nodes and some fake nodes that won't even supply you with a chain let alone contribute to a speed up.

[ranochigo]

You can lock the thread if you don't want any replies, though I'm not sure why you would want to do that.

I'm not going to suggest anything to help you synchronize quicker since you said so in the OP. Bitcoin Core's P2P protocol is fairly well established and I've always had an abundance of nodes to connect to after my client retrieves it from the DNS seeds. How do you think we can improve on that? Could you make a pull request on that topic if you have any good ideas?

I can supply you with a pre-validated data directory which would pretty much cut down your bottleneck to your I/O and also the download speed. The question lies with, are you willing to trust me? I'm just a stranger on the internet and you wouldn't know if I edited the chainstate to include transactions that wouldn't exist.

Ps. Just because you're having some problems doesn't mean the whole system is problematic.

[20kevin20]

Bitcoin still is the currency of the people. If you don't like having a cryptocurrency with a verifiable history from inception 'till this date, then just switch over to another centralized shitcoin or leave the space. BTC will probably never be a perfect currency and we have to either accept that or go away.

I admit that the current blockchain size is just too large for the average person to afford running a full node on their own, but we only need time and someone will most likely come up at one point with a solution. Either that or the tech will advance fast enough for a 2TB HDD/SSD to become as affordable as today's 64GB microSDs.