They've both sync'd now, and went fairly quickly towards the end.
I'm quite impressed with the new rig. It's ideal as a light full function notebook with up to 11 hours battery life, and the ability to run a full node with the complete blockchain.
Topic: Is Bitcoin over active at the moment (Read 631 times)
Thanks for that Shorena.
They've both sync'd now, and went fairly quickly towards the end.
I'm quite impressed with the new rig. It's ideal as a light full function notebook with up to 11 hours battery life, and the ability to run a full node with the complete blockchain.
They've both sync'd now, and went fairly quickly towards the end.
I'm quite impressed with the new rig. It's ideal as a light full function notebook with up to 11 hours battery life, and the ability to run a full node with the complete blockchain.
It seems to have speeded up now. I ran both nodes at the same time, and it only appeared to knock about 2Kb off the speed of each.
Something may be going on around here, because my mobile couldn't connect - it said the service was overloaded. ( that's got nothing to do with the WiFi of course ).
Something may be going on around here, because my mobile couldn't connect - it said the service was overloaded. ( that's got nothing to do with the WiFi of course ).
If they are in the same network they should connect to eachother. You can also add mine[1] or other nodes you know are always online and fast (enough) for you via your bitcoin.conf file. Just add lines like the following to the file[2].
Code:
# Use as many addnode= settings as you like to connect to specific peers
#addnode=10.0.0.2:8333
addnode=188.68.53.44
#addnode=10.0.0.2:8333
addnode=188.68.53.44
[1] 188.68.53.44
[2] Create it in the same dir your wallet.dat is if needed.
It seems to have speeded up now. I ran both nodes at the same time, and it only appeared to knock about 2Kb off the speed of each.
Something may be going on around here, because my mobile couldn't connect - it said the service was overloaded. ( that's got nothing to do with the WiFi of course ).
Something may be going on around here, because my mobile couldn't connect - it said the service was overloaded. ( that's got nothing to do with the WiFi of course ).
My new wallet went from 24 hours behind to 25 hours behind. I switched to the old wallet on my main computer, and that doesn't seem to be catching up either. I'm on public WiFi which is reported to be giving me a 30Kb connection. This has been fast enough in the past, but it looks as if it may be struggling at the moment.
If Bitcoin traffic is going to increase, then I may have to rethink my approach to running a node.
If Bitcoin traffic is going to increase, then I may have to rethink my approach to running a node.
https://blockchain.info/unconfirmed-transactions
66067
stuck
I've got 2 core 0.13.2 nodes.
i know you dont love BU/XT/classic and other implementations.
but atleast find some core nodes that are uptodate and addnode them. thus you are not delaying yourself by only limiting your exposure to the network of leachers who are not uptodate, which can then cause you to not be uptodate
I've got 2 core 0.13.2 nodes.
I would not be surprised if someone or a group of people might be targeting nodes with DDoS / Ping of Death attacks, but that is just
the conspiracy theorist in me. Just as a matter of interest, what client are you running? If more people start reporting that this is the
case, then we would know something is up.
the conspiracy theorist in me. Just as a matter of interest, what client are you running? If more people start reporting that this is the
case, then we would know something is up.
My new wallet went from 24 hours behind to 25 hours behind. I switched to the old wallet on my main computer, and that doesn't seem to be catching up either. I'm on public WiFi which is reported to be giving me a 30Kb connection. This has been fast enough in the past, but it looks as if it may be struggling at the moment.
If Bitcoin traffic is going to increase, then I may have to rethink my approach to running a node.
If Bitcoin traffic is going to increase, then I may have to rethink my approach to running a node.
problem may also be that you admit(in another topic) that you are overtly happy to use the node ban hammer too much. meaning you probably are not getting a good supply of reliable nodes to sync from.
try searching for other nodes that are upto date.
search bitnodes.io for nodes that are upto-date that meet your "favourite brand" criteria. and "addnode" them.
Thanks Danny - I do tend to watch political stuff on YouTube whilst it's sync'ing. But I would have thought that if it's showing 30Kb, then that should be OK. Your point about processing power is valid as well. Windows keeps adding processes, and they may be messing things up.
My new wallet went from 24 hours behind to 25 hours behind. I switched to the old wallet on my main computer, and that doesn't seem to be catching up either. I'm on public WiFi which is reported to be giving me a 30Kb connection. This has been fast enough in the past, but it looks as if it may be struggling at the moment.
If Bitcoin traffic is going to increase, then I may have to rethink my approach to running a node.
If Bitcoin traffic is going to increase, then I may have to rethink my approach to running a node.
At 30Kbps, you should be able to download a block every 35 seconds or so.
On average a new block is created every 10 minutes, so if you are 25 hours behind then you are about 150 blocks behind. It should take you about an hour-and-a-half to download those 150 blocks at that speed.
If it is taking longer than that, then you are most likely connected to some peers that have slower connections or that aren't sending you any usable blocks. It's also possible that you are downloading the blocks fast enough, but that you don't have enough processing power on your computer to verify them very fast.
I live in a quite remote area, my connection used to be good enough but now my Bitcoin Core wallet always freezes when behind & downloading to catch up with new blocks.
I have to do it at my parents house which is a pain in the ass.
I have to do it at my parents house which is a pain in the ass.
My new wallet went from 24 hours behind to 25 hours behind. I switched to the old wallet on my main computer, and that doesn't seem to be catching up either. I'm on public WiFi which is reported to be giving me a 30Kb connection. This has been fast enough in the past, but it looks as if it may be struggling at the moment.
If Bitcoin traffic is going to increase, then I may have to rethink my approach to running a node.
If Bitcoin traffic is going to increase, then I may have to rethink my approach to running a node.
Jump to: