GoldCoin TestNet Round #2 for the New Client

[Stouse49]

There are two versions to use in the testnet.

• The Old Client - 0.7.5
• The New Client - 0.14.2

Install the software
The install packages are zip files.  They contain the programs and folders that will be used for the blockchain.  It doesn't interfere with other wallets on your system.  Unzip these folders where you want and run the "1. start-client" command.  Other commands such as mining may be present in the packages.   If you delete the package after unzipping and running the client, you will loose your wallet.

Windows
old - https://github.com/Stouse49/goldcoin/releases/download/vv0.7.5.0-testnet/Windows.GoldCoin.0.7.5.TestNet.zip
new - https://github.com/Stouse49/Goldcoin-GLD/releases/download/v0.14.2.1-testnet-march/Windows.GoldCoin.Core.0.14.2.1.TestNet-march.zip

Mac
old - https://github.com/Stouse49/goldcoin/releases/download/vv0.7.5.0-testnet/Mac.GoldCoin.0.7.5.TestNet.zip (may not connect)
new -

Linux

Mining
Information to be added later.

Super Users (Exchanges, Mining Pools, etc)

Source Code:
old:  https://github.com/Stouse49/goldcoin [branch = testnet]
Build instructions: https://www.goldcointalk.org/index.php?topic=3764.msg18102#msg18102

new:  https://github.com/Stouse49/Goldcoin-GLD [branch = testnet]
Build instructions:  https://github.com/goldcoin/Goldcoin-GLD/tree/goldcoin-master/doc

Mining
old - solo - https://github.com/pooler/cpuminer,

Code: [Select]

$ minerd -o 127.0.0.1:<rpc port, default=18121> -u <user> -p <password> -t <threads, such as 2>new - Solo - https://github.com/mikeghen/litecoin-solo-mining-tutorial

server.js - example

Code: [Select]

var myCoin = {
    "name": "Goldcoin",
    "symbol": "GLD",
    "algorithm": "scrypt",
     "peerMagic": "fdc2b4dd",
     "peerMagicTestnet": "fcc5b4dd"
};

var Stratum = require('stratum-pool');

var pool = Stratum.createPool({

    "coin": myCoin,

    "auxes": [],

    "address": "n33ZW9SXvtCXRvsP7gjQqYFaEwxwpXoWpC", //Address to where block rewards are given

    /* Block rewards go to the configured pool wallet address to later be paid out to miners,
       except for a percentage that can go to, for examples, pool operator(s) as pool fees or
       or to donations address. Addresses or hashed public keys can be used. Here is an example
       of rewards going to the main pool op, a pool co-owner, and NOMP donation. */
    // "rewardRecipients": {
    //     "n37vuNFkXfk15uFnGoVyHZ6PYQxppD3QqK": 1.5, //1.5% goes to pool op
    //     "mirj3LtZxbSTharhtXvotqtJXUY7ki5qfx": 0.5, //0.5% goes to a pool co-owner
    // },

    "blockRefreshInterval": 1000, //How often to poll RPC daemons for new blocks, in milliseconds


    /* Some miner apps will consider the pool dead/offline if it doesn't receive anything new jobs
       for around a minute, so every time we broadcast jobs, set a timeout to rebroadcast
       in this many seconds unless we find a new job. Set to zero or remove to disable this. */
    "jobRebroadcastTimeout": 55,

    /* Some attackers will create thousands of workers that use up all available socket connections,
       usually the workers are zombies and don't submit shares after connecting. This features
       detects those and disconnects them. */
    "connectionTimeout": 1200, //Remove workers that haven't been in contact for this many seconds

    /* Sometimes you want the block hashes even for shares that aren't block candidates. */
    "emitInvalidBlockHashes": false,

    /* Enable for client IP addresses to be detected when using a load balancer with TCP proxy
       protocol enabled, such as HAProxy with 'send-proxy' param:
       http://haproxy.1wt.eu/download/1.5/doc/configuration.txt */
    "tcpProxyProtocol": false,

    /* If a worker is submitting a high threshold of invalid shares we can temporarily ban their IP
       to reduce system/network load. Also useful to fight against flooding attacks. If running
       behind something like HAProxy be sure to enable 'tcpProxyProtocol', otherwise you'll end up
       banning your own IP address (and therefore all workers). */
    "banning": {
        "enabled": true,
        "time": 600, //How many seconds to ban worker for
        "invalidPercent": 50, //What percent of invalid shares triggers ban
        "checkThreshold": 500, //Check invalid percent when this many shares have been submitted
        "purgeInterval": 300 //Every this many seconds clear out the list of old bans
    },

    /* Each pool can have as many ports for your miners to connect to as you wish. Each port can
       be configured to use its own pool difficulty and variable difficulty settings. varDiff is
       optional and will only be used for the ports you configure it for. */
    "ports": {
        "3333": { //A port for your miners to connect to
            "diff": 32, //the pool difficulty for this port

            /* Variable difficulty is a feature that will automatically adjust difficulty for
               individual miners based on their hashrate in order to lower networking overhead */
            "varDiff": {
                "minDiff": 8, //Minimum difficulty
                "maxDiff": 512, //Network difficulty will be used if it is lower than this
                "targetTime": 15, //Try to get 1 share per this many seconds
                "retargetTime": 90, //Check to see if we should retarget every this many seconds
                "variancePercent": 30 //Allow time to very this % from target without retargeting
            }
        },
        "3256": { //Another port for your miners to connect to, this port does not use varDiff
            "diff": 256 //The pool difficulty
        }
    },

    /* Recommended to have at least two daemon instances running in case one drops out-of-sync
       or offline. For redundancy, all instances will be polled for block/transaction updates
       and be used for submitting blocks. Creating a backup daemon involves spawning a daemon
       using the "-datadir=/backup" argument which creates a new daemon instance with it's own
       RPC config. For more info on this see:
          - https://en.bitcoin.it/wiki/Data_directory
          - https://en.bitcoin.it/wiki/Running_bitcoind */
    "daemons": [
        {   //Main daemon instance
            "host": "127.0.0.1",
            "port": 19332,
            "user": "Stouse49",
            "password": "x"
        }
        // {   //Backup daemon instance
        //     "host": "127.0.0.1",
        //     "port": 19344,
        //     "user": "litecoinrpc",
        //     "password": "testnet"
        // }
    ],


    /* This allows the pool to connect to the daemon as a node peer to receive block updates.
       It may be the most efficient way to get block updates (faster than polling, less
       intensive than blocknotify script). It requires the additional field "peerMagic" in
       the coin config. */
    "p2p": {
        "enabled": false,

        /* Host for daemon */
        "host": "127.0.0.1",

        /* Port configured for daemon (this is the actual peer port not RPC port) */
        "port": 18121,

        /* If your coin daemon is new enough (i.e. not a [beep]coin) then it will support a p2p
           feature that prevents the daemon from spamming our peer node with unnecessary
           transaction data. Assume its supported but if you have problems try disabling it. */
        "disableTransactions": true

    }

}, function(ip, port , workerName, password, callback){ //stratum authorization function
    console.log("Authorize " + workerName + ":" + password + "@" + ip);
    callback({
        error: null,
        authorized: true,
        disconnect: false
    });
});

pool.on('share', function(isValidShare, isValidBlock, data){

    if (isValidBlock)
        console.log('Block found');
    else if (isValidShare)
        console.log('Valid share submitted');
    else if (data.blockHash)
        console.log('We thought a block was found but it was rejected by the daemon');
    else
        console.log('Invalid share submitted')

    console.log('share data: ' + JSON.stringify(data));
});

pool.on('log', function(severity, logKey, logText){
    console.log(severity + ': ' + '[' + logKey + '] ' + logText);
});

console.log("Starting Pool")
pool.start();
console.log("Pool started", pool)

[Stouse49]

Please Join In on the TestNet part 2.  This test should last about 1 week, unless we find some serious bugs!

My new address:  mn1fqhdZYVhCrwTyJj5sRp8bwEXgFyjF3P

[fwhite]

ok new client running
my testnet address; mr3maCb6SsBRLWh8kxoPteFukL3h9zo2j7

[TestingCrypto]


v0.14.2.1-cfc63da
C:\Users\DLL\AppData\Roaming\Goldcoin\testnet4
Sun Feb 4 22:06:47 2018

{
  "version": 140201,
  "protocolversion": 70015,
  "walletversion": 130000,
  "balance": 0.00000000,
  "blocks": 2202,
  "timeoffset": 0,
  "connections": 4,
  "proxy": "",
  "difficulty": 0.0005285899106958497,
  "testnet": true,
  "keypoololdest": 1517803286,
  "keypoolsize": 100,
  "paytxfee": 0.00000000,
  "relayfee": 0.00100000,
  "errors": "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"
}

n4KmFYsyvHLZA9TMxJGuiPj3yaCVr2Thyy
n1eAMP1SAbvkmKCPgwGq4PBvadovQXwiPB

Status: 4/unconfirmed
Date: 2/4/2018 23:09
Source: Generated
Credit: 5.00000000 GLD (matures in 97 more blocks)
Net amount: 0.00000000 GLD
Transaction ID: 6f75f62a5d581e1459993e4bb2c8dcf0fd71a1ccff352fa83394787a02ae7e3b
Transaction total size: 90 bytes
Output index: 0

Generated coins must mature 101 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours

{
  "blocks": 2237,
  "currentblocksize": 0,
  "currentblockweight": 0,
  "currentblocktx": 0,
  "difficulty": 0.0005285899106958497,
  "errors": "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications",
  "networkhashps": 18347.29198630137,
  "pooledtx": 0,
  "chain": "test"
}


[Miki77]

Problem.

[fwhite]

Problem.

You should not modify the scripts provided in the zip file I think, just follow the instructions from the first post.

Steps;
Unzip Windows GoldCoin 0.7.5 TestNet.zip to a folder
Start the client with 1. start-client.cmd
Wait a bit (1 minute)
Start the miner with 2. start-mining-CPU.cmd

Miner should show something like this

Code: [Select]

Goldcoin 0.7.5 TestNet Mining with cpuminer (slow)
[2018-02-06 16:55:03] Binding thread 0 to cpu 0
[2018-02-06 16:55:03] Binding thread 1 to cpu 1
[2018-02-06 16:55:03] 4 miner threads started, using 'scrypt' algorithm.
[2018-02-06 16:55:03] Binding thread 2 to cpu 2
[2018-02-06 16:55:03] Binding thread 3 to cpu 3
[2018-02-06 16:55:03] No payout address provided, switching to getwork
[2018-02-06 16:55:04] thread 2: 4104 hashes, 17.51 khash/s
[2018-02-06 16:55:04] thread 3: 4104 hashes, 17.51 khash/s
For the 0.14.2.1 client the same steps.

[cryptosolar]

-started to mine on the old client, with  = start-mining-CPU.cmd

switched mining

-start mining now on the goldcoinpool.com with new client using my gpu and cgminer 3.7.2.

edit:


i ve only made a few changes:
if you want to something during mining then use a lower itensity, if you want to run it during the night, you can use a higher intensity.
worksize changed to 256
thread concurrency changed to 2048

[Stouse49]

Problem.

You are trying to mine with cpuminer and the new client.  This doesn't work and it only possible with the old client.

To mine with the new client, connect to the pool:  http://goldcoinpool.com or you must perform complicated instructions to mine solo here:  https://github.com/mikeghen/litecoin-solo-mining-tutorial

[Miki77]

Problem.

You are trying to mine with cpuminer and the new client.

Yes.

This doesn't work and it only possible with the old client.

I did not know that.

Thanks for clarification.

[Stouse49]

Mining is no longer working with the old client, by design.  You can try to mine with the old client and let me know if any blocks are mined and accepted.

[Miki77]

Yes, it does not work, too.



There were 5 immature coins for just one block, nothing more.

[Stouse49]

Yes, it does not work, too.

Thank you for confirming.  The old client will show that it tried to mine blocks, but they are not confirmed.  At one point the old client on my system had 3 blocks  that were confirming (but they were later orphaned). 

[MicroGuy]

Before we can release the new wallet, we need more testing of transactions between old and new clients. It's important that the community do some of this testing because otherwise a bug could go overlooked..

Please ask any questions and post results below.

[fwhite]

I did several transactions between the old and new client last week, with and without fee etc.
No errors.

[Miki77]

Got from MG 3500 GLDs to check transaction between old and new wallet.

Result:

http://18.216.202.150:8001/address/miKy57HgsgJPUxXCcFJB3W2NVMd1YGKJco