Example of a PPCoin Config file ppcoin.conf

[FuzzyBear]

# 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

# ... 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=INPUT_YOUR_USERNAME_HERE
rpcpassword=INPUT_YOUR_PASSWORD_HERE

# 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

[Ikea_Meatballs]

+:)

[kalon]

If possible, some further commenting to describe what some of these are for an whether they are necessary to set would be helpful to people less familiar with how it works. I like to think I'm up on stuff but that'd include me. 

[davidpbrown]

The .conf I have is principally the same for all Alt-TC.

So, for PPC is

Code: [Select]

rpcuser=someusername
rpcpassword=somerandompassword
rpcport=9902
daemon=1
with one exception; for PPC, I also have this line there too:

Code: [Select]

server=1
The server=1, allows me to then run a commandline

Code: [Select]

ppcoind walletpassphrase MyWalletUnlockPassword 9999999 trueand have the "unlocked for block minting only" message over the lock, which apparently in time will let the interest accrue.

I'm not sure you even need the rpcport, if you aren't looking to port-forward from your router more requests than the usual 8 connections.

Serious Proof of Work mining is not something I've tried, having been put off by recognising I haven't got the hardware for it. If you were to mine, then there are plenty of guides for that from pools looking for your contribution that would encourage use of the other options above. I think I've seen it suggest one of them is a count of the number of CPUs available for example but not needed or useful if you're just holding coins and spending them.

[xjabc]

Great introduction. It's very helpful.

[ASIC PPC]

Thanks for this Fuzz! I see you doing a lot for PPC keep up the good work

[Dini]

The .conf I have is principally the same for all Alt-TC.

The server=1, allows me to then run a commandline

Code: [Select]

ppcoind walletpassphrase MyWalletUnlockPassword 9999999 trueand have the "unlocked for block minting only" message over the lock, which apparently in time will let the interest accrue.

Serious Proof of Work mining is not something I've tried, having been put off by recognising I haven't got the hardware for it. If you were to mine, then there are plenty of guides for that from pools looking for your contribution that would encourage use of the other options above. I think I've seen it suggest one of them is a count of the number of CPUs available for example but not needed or useful if you're just holding coins and spending them.

David Brown,
I'm confused because I thought the benefit of Peercoin was that mining does not require much computing power, just luck, that's why we can put the mining software on inexpensive computers, no special hardware requirements.  Or, is it just minting, but not mining, that is energy efficient for getting coins?  There seems to be conflicting info on this. 

[bigkesh]

Didn't read the thread, but I'm sure it's very good. I just need to post two replies. This is the second one. Sorry.

[lllllll]

The .conf I have is principally the same for all Alt-TC.

The server=1, allows me to then run a commandline

Code: [Select]

ppcoind walletpassphrase MyWalletUnlockPassword 9999999 trueand have the "unlocked for block minting only" message over the lock, which apparently in time will let the interest accrue.

Serious Proof of Work mining is not something I've tried, having been put off by recognising I haven't got the hardware for it. If you were to mine, then there are plenty of guides for that from pools looking for your contribution that would encourage use of the other options above. I think I've seen it suggest one of them is a count of the number of CPUs available for example but not needed or useful if you're just holding coins and spending them.

David Brown,
I'm confused because I thought the benefit of Peercoin was that mining does not require much computing power, just luck, that's why we can put the mining software on inexpensive computers, no special hardware requirements.  Or, is it just minting, but not mining, that is energy efficient for getting coins?  There seems to be conflicting info on this.

I would be really interested to read the answer of an expert to this question

[gmaslin]

Where is this configuration file in Windows (Vista and 7) and where is it in Linux?