FWIW:
Alpha release of an implementation of the 0.16.3 reference client for the Gapcoin network:
https://github.com/gjhiggins/gapcoin-core/releases/tag/v0.1rc-alpha, testnet-only while we test the robustness and reliability of the implementation. Linux, Windows64 and OSX binaries available. Client can be built from cloned github repos -
https://github.com/gjhiggins/gapcoin-core.
Copy the provided
gapcoin.conf into the data directory. (In order to have the mining page slider bar show the maximum threads available for your machine, comment out the
genproclimit line or set a higher limit as desired).
For Windows users, if you want to use a separate data directory for the 0.16.3 client such as
C:\Users\\AppData\Roaming\GapcoinCore then click on "Properties" of a shortcut to the 0.16.3 client
gapcoin-qt.exe and add
-datadir=C:\Users\\AppData\Roaming\GapcoinCore at the end, e.g.
C:\Program Files (x86)\Gapcoin\gapcoin-qt.exe -datadir=C:\Users\\AppData\Roaming\GapcoinCore.
Please be advised - if not configured with
-testnet on the command line or
testnet=1 in the config file, the 0.16.3 reference client
will connect to the current mainnet and
will act as a processing node but the more advanced/complex transactions created by the 0.16.3 client will not be recognized/process/broadcast by the current population on 0.9.4 clients and the originating 0.16.3 client will probably find itself on a singleton fork, necessitating zeroing of the data dir and subsequent resync (so don't try it).
Cheers
Graham
Early indications are that changing the
txindex setting requires a clearout of the datadir and a resync.
Edit: I found that on Windows 10 at least, so when I created a testnet-specific shortcut, I needed to separate the arguments and surround them in double quotes (I'm using a Vagrant box VM, so I am user "Vagrant") and the entire content of the "Shortcut" field was:
"C:\Program Files (x86)\Gapcoin\gapcoin-qt.exe" "-testnet" "-datadir=C:\Users\Vagrant\AppData\Roaming\Gapcoin" 
