[SOLVED] ppcoind and dumping/importing private keys

[mebezac]

I'm running the latest version of PPCoin on Windows 8 64bit but can't seem to get ppcoind.exe up and running. I made the ppcoin.conf and added an rpc user and password. I open a command prompt in the daemon directory and then type

Code:

ppcoind

and then it just sits there, I can't type into it. I am doing something wrong?

Also, if I type

Code:

ppcoind help

it just returns

Code:

error: couldn't connect to server

My end goal after getting ppcoind to work is to dump my private key and also import some private keys.

Thanks for any help you can offer.

Also, if needed here's my ppcoin.conf: (I removed the rpc password, it's not blank in my file)

Code:

# ppcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the production ppcoin network.
#testnet=0

# Connect via a socks4 proxy - default none
#proxy=127.0.0.1:9050
# Accepting incoming connections
listen=1
# Enable UPnP negotiation with router/firewall to accept incoming connections
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

# ... 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=8


# JSON-RPC options (for controlling a running ppcoind process)

#Server mode allows Qt to accept JSON-RPC commands
server=0

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=bitcoinrpc
rpcpassword=

# How many seconds ppcoin 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=10.1.1.34
#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=0

# Use SSE instructions to try to generate ppcoins faster with built-in CPU mining
#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

[1715407686]

1715407686

[1715407686]

1715407686

[1715407686]

1715407686

[1715407686]

1715407686

[1715407686]

1715407686

[1715407686]

1715407686

[Sunny King]

I'm running the latest version of PPCoin on Windows 8 64bit but can't seem to get ppcoind.exe up and running. I made the ppcoin.conf and added an rpc user and password. I open a command prompt in the daemon directory and then type

Code:

ppcoind

and then it just sits there, I can't type into it. I am doing something wrong?

Also, if I type

Code:

ppcoind help

it just returns

Code:

error: couldn't connect to server

My end goal after getting ppcoind to work is to dump my private key and also import some private keys.

Thanks for any help you can offer.

Also, if needed here's my ppcoin.conf: (I removed the rpc password, it's not blank in my file)

Code:

# ppcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the production ppcoin network.
#testnet=0

# Connect via a socks4 proxy - default none
#proxy=127.0.0.1:9050
# Accepting incoming connections
listen=1
# Enable UPnP negotiation with router/firewall to accept incoming connections
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

# ... 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=8


# JSON-RPC options (for controlling a running ppcoind process)

#Server mode allows Qt to accept JSON-RPC commands
server=0

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=bitcoinrpc
rpcpassword=

# How many seconds ppcoin 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=10.1.1.34
#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=0

# Use SSE instructions to try to generate ppcoins faster with built-in CPU mining
#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

On Windows you have to open another cmd window to query it. The first one is running.

[dreamwatcher]

With Windows you will need two command line windows, one to start the daemon in and the other to issue commands. You could also start the GUI version, and open one command line window to issue commands.

Window handles the daemons different then Linux. If you start a daemon in the command line window, it is essence becomes that command line window, unlike Linux which will put you back at the CLI if you use the --daemon switch.

So with either a command line window running the daemon or running the GUI version with the server=1 option in the ppcoin.conf, start a command line window in the ppcoin daemon directory and just type in:

ppcoind <command>

The commands for import and export of keys:

ppcoind importprivkey <private key> [account name]

ppcoind dumpprivkey <account address>

If you have an encrypted wallet you will need to unlock it first with:

ppcoind walletpassphrase <password> <time>

The time is in milliseconds, and lock resets when the daemon is shutdown.

 

[mebezac]

Makes sense. Thanks guys!

[chriswen]

# Miscellaneous options

# Set gen=1 to attempt to generate ppcoins using built-in CPU mining
#gen=0

# Use SSE instructions to try to generate ppcoins faster with built-in CPU mining
#4way=1

Are these automatically set to generate ppcoins?

[Sunny King]

# Miscellaneous options

# Set gen=1 to attempt to generate ppcoins using built-in CPU mining
#gen=0

# Use SSE instructions to try to generate ppcoins faster with built-in CPU mining
#4way=1

Are these automatically set to generate ppcoins?

No. By default the built-in cpu mining is turned off. I think mining by cpu at this point is a waste of energy and likely a losing proposition, unless someone else pays the electricity bill