how come the block chain takes so long to download on pcc wallet with no status bar. mine just says warning, checkpoint is to old. wait for block to download.
Hi, I am currently in the same situation, no blockchain downloaded. I have been trying using the telnet trick connecting to the port 8333 to check if it was blocked by any firewall, but it is not the case.
If anyone has an idea on how to proceed, it will be great. Below is my PPCoin.conf, if anyone find an error, thanks for reporting :
MichelG
ppcoin.conf configuration file. Lines beginning with # are comments.
Network-related settings:
Run on the test network instead of the real bitcoin network.
#testnet=0
Connect via a socks4 proxy - default none
#proxy=127.0.0.1:9050
Accepting incoming connections
listen=1
UPnP
#upnp=1
##############################################################
Quick Primer on addnode vs connect
Let’s say for instance you use addnode=4.2.2.4
addnode will connect you to and tell you about the
nodes connected to 4.2.2.4. In addition it will tell
the other nodes connected to it that you exist so
they can connect to you.
connect will not do the above when you ‘connect’ to it.
It will only connect you to 4.2.2.4 and no one else.##
So if you’re behind a firewall, or have other problems
finding nodes, add some using ‘addnode’.
If you want to stay private, use ‘connect’ to only
connect to “trusted” nodes.
If you run multiple nodes on a LAN, there’s no need for
all of them to open lots of connections. Instead
‘connect’ them all to one node that is port forwarded
and has lots of connections.
Thanks goes to [Noodle] on Freenode.
##############################################################
Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333
addnode=seed.bitcoin.sipa.be
addnode=dnsseed.bluematt.me
addnode=dnsseed.bitcoin.dashjr.org
addnode=66.90.146.146
addnode=91.156.102.128
addnode=110.174.124.20
addnode=67.14.164.114
addnode=37.209.40.22
addnode=50.71.216.165
addnode=109.108.236.208
addnode=173.28.37.150
addnode=68.102.86.156
addnode=213.251.187.24
addnodd=188.134.122.31
addnode=72.38.179.122
… or use as many connect= settings as you like to connect ONLY
to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333
Maximum number of inbound+outbound connections.
#maxconnections=
JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
server=1 tells Bitcoin-QT to accept JSON-RPC commands.
#server=0
You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=THIS_IS_MY_PRIVATE_USERNAME_PUT_YOURS
rpcpassword=THIS_IS_MY_PRIVATE_PASSWORD_PUT_YOURS
How many seconds bitcoin will wait for a complete RPC HTTP request.
after the HTTP connection is established.
#rpctimeout=30
By default, only RPC connections from localhost are allowed. Specify
as many rpcallowip= settings as you like to allow connections from
other hosts (and you may use * as a wildcard character):
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
Listen for RPC connections on this TCP port:
rpcport=9902
You can use ppcoind to send commands to ppcoind
running on another host using this option:
rpcconnect=127.0.0.1
Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
with ppcoind
#rpcssl=1
OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem
Miscellaneous options
Set gen=1 to attempt to generate ppcoins using built-in CPU mining
#gen=1
Use SSE instructions to try to generate bitcoins faster.
#4way=1
Pre-generate this many public/private key pairs, so wallet backups will be valid for
both prior transactions and several dozen future transactions.
#keypool=100
Pay transaction fee amount per kilo-byte. Default 0.01 (1 cent)
Minimum required 0.01 (1 cent)
#paytxfee=0.01
Allow direct connections for the ‘pay via IP address’ feature.
#allowreceivebyip=1
Issue fixed. I have no idea how, has nothing changed in my config, neither rebooted the PC.
Michel.