Bitcoin Forum

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

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

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=<A username>
rpcpassword=<A random password>

#The reserve balance field is the minimum amount of coins you want to have available and NOT put up as stake.  
#The reason for this is that if you are generating proof of stake you cannot spend those coins for 520 blocks.
#reservebalance=10000

@echo off
@echo Enter PPC password...
SET /P variable=Password : 
ppcoind walletpassphrase %variable% 9999999 true

C:\Users\dv\Downloads\PPCoin-0.3.0\daemon>ppcoind.exe getmininginfo
{
    "blocks" : 44845,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 348773.05554859,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "pooledtx" : 0,
    "testnet" : false
}

c:\Program Files (x86)\PPCoin\daemon>mint
Enter PPC password...
Password : xxxxxxxxxxx
error: {"code":-17,"message":"Error: Wallet is already unlocked, use walletlock
first if need to change unlock settings."}

c:\Program Files (x86)\PPCoin\daemon>

# 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:9950
# 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

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

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

# 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=
rpcallowip=
rpcallowip=
rpcallowip=
rpcallowip=
rpcallowip=
# 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 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

server=1

rpcuser=<xxxxxxx>
rpcpassword=<xxxxxxxxxxx>

reservebalance=10000

@echo off
@echo Enter PPC password...
SET /P XXXXXXXX=Password : 
ppcoind walletpassphrase %XXXXXXXX% 9999999 tru

#!/bin/bash

stty -echo
read -p "rpc: " rpcpass; echo
read -p "wal: " walpass; echo
./ppcoind -rpcpassword=$rpcpass walletpassphrase $walpass 99999999 true
stty echo

#!/bin/bash

stty -echo
read -p "rpc: " rpcpass; echo
./ppcoind -rpcpassword=$rpcpass $1 $2 $3 $4 $5 $6 $7 $8 $9
stty echo