Gridcoinresearch config file
What should I put in my config-file for Gridcoin-Research?
Please find gridcoinresearch.conf in your %appdata%\roaming\gridcoinresearch folder (Linux: ~/.GridcoinResearch) and insert a line for your BOINC email address and at least one node if it is empty:
These lines should already suffice for the GUI client. If you would like to control the daemon through command line, you will need to add:
This is set to localhost for default, so telnet in the local cmd works fine. Remote control however requires to set rpcallowip to the right value.
For command line administration, you will also need to enter a username and password into your config file:
Additionally, Gridcoin will listen for commands on whichever port you specify with rpcport if, for instance, you would like to control gridcoin directly from another host. For example:
Default port is 32749.
If your BOINC Data folder is not in the default path, you need to specify its location in the config file. The following is an example of a non-default path. The double backslashes are necessary, especially at the end of the path. eg:
or on GNU/Linux (notice trailing slash):
If your system fails to sync, check your List of Addnodes.
But ensure you dont have an addnode=your own ip, or you will end up banning yourself (because when the node sends itself the first message, the local time is far enough off of the network time (which it does not know yet) so it will ban itself.
If you need help with the new Proof of Research client, find us at: https://cryptocointalk.com/topic/18805-gridcoin-proof-of-research-information-and-support/
Most of Gridcoin's config file flags and command line arguments are taken directly from Bitcoin, and you can find a list which explains a lot of these options here: https://en.bitcoin.it/wiki/Running_Bitcoin A few additions which are specific to Gridcoin are listed below:
This is a toggle switch for you to accept connections from outside. Enabling this option will allow you to participate as a fullnode and spare extra bandwidth for the gridcoin network.
Those with less RAM and slower systems might wish to add listen=0 to their config to NOT allow incoming connections if the firewall is not already blocking them.
The default listen port is 32749.
Still having problems to get connections? Maybe use netstat to check your network statistic, see what is coming in and out/what processes are involved, etc:
win: http://technet.microsoft.com/en-us/library/ff961504.aspx (switch -o is useful as it shows the associated PID (Process IDentifier). Once you have that you can go to Task Manager>services and cross reference the PID) linux: http://www.tecmint.com/20-netstat-commands-for-linux-network-management/ mac: http://www.macosxtips.co.uk/index_files/how-to-use-network-utility.php
auto unlock feature - use encrypted wallet for staking
since we do not have or want to store your passphrase anywhere so here is how to test this feature:
Go to RPC. Type:
execute encrypt YourPassPhrase
You will receive an encrypted string in the rpc (Only decryptable by jumping through hoops with AES512/base64 - i.e. if this phrase is compromised by a thief and the wallet is locked, it would take them quite a while to figure out how to decrypt the passphrase).
Modify the config file
Save and restart.
Test by telling us when the client starts to stake, the config log should not show "unable to mine, wallet locked".
GRC will export mags to CSV once per day.
client does no longer upgrade/reboot on its own.
prevent wallet from talking to you.
turns off d-dos security in GRC client.
let your node receive tons of extra messages in debug.log and debug2.log. If you lose disk space you can set debug=false in the config file and delete your debug.log. After version 126.96.36.199 Gridcoin shrinks its debug.logs every time you boot down to about 150k, so it should technically stay very manageable from this point forward.
a way for tester to focus on up to date issues in a succinct manner - but you don't have to set it as it will just wretch out a lot of stuff that rob is working on...
on invalid checkpoints do not enter safemode, but retry.
option to let you decide if you want to see the orphaned transactions in your transaction list - helpful for debugging them. usually, coinstake transactions that are not in the main chain are removed from the list.
stop client from automated restarting.
became default, If anyone wants the wallet to reboot after it reorganizes the chain they will have to add suppressreboot=false
seems to prevent crashes rather than supressrestart.