someone could post some nodes?
Slow sync? Adding more nodes is unlikely to help - chances are you're probably already connected to several. See these earlier messages, including the link to the bootstrap:
lots of this sort of thing in the logs
peer 72.80.55.214:50145: leap backwards in height request, from max 1738831 to current 280001. penalty=6/100
perhaps we have misbehaving nodes messing things up a bit?
peer 72.80.55.214:50145: leap backwards in height request, from max 1738831 to current 280001. penalty=6/100
perhaps we have misbehaving nodes messing things up a bit?
I'd say that's a side effect of the out-of-control way that CLAM syncs. This has been a problem for some time and manifests itself as a sync stalling. You need to keep stopping and restarting the client to kick it back into action. The code which emits that error doesn't really fix the problem, it just bans clients that go a little too wild. Unfortunately it's normal.
Need node list, takes days to update blockchain, last 5-6 weeks...
See the msg I posted above a couple of hours ago. This is a known and ongoing problem with the CLAM client. Adding nodes won't help.
Your best bet is the bootstrap: https://s3.amazonaws.com/dooglus/bootstrap.dat
That will give you a head start, but the client will still have to catch up with any new blocks.
Along with the above suggestions, I found only connecting to 1-2 nodes while syncing helped. (helps keep the orphan count low) Also keeping an eye on the debug file, and restarting the client when I got 751 orphans, or connection issues, helped. It's still a slow process but can be done. Once your synced you can increase the number of connections.
