Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
$ 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-tutorialvar 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)
Downloaded the updated client as Greg suggested on Telegram, started it but it says 7 weeks behind and its not finding nodes.
Also, there is still a Litecoin icon in the Help menu -> About Goldcoin Core.
okay
deleted the old client
downloaded the client again
the pool should be also up to date now.
Is there a node to add ?
I bought coins yesterday on cryptopia, can I transfer them to a new purse when it is ready?
I can only do what I can do with what I have to do it with. Right now, anyway.
But, I am seeing accepted shares 11/11 with the green "yes!" on the same line in the interface.
So, how do I interpret that?
I just want to be productive and so if I have to mine another coin to use to buy GLD with, I will.
Just need some advice.
[Still have not gotten an explanation as to why address is not showing on "Workers" tab.
I'm not pool hopping and intend to stay for the long blocks, so...?]
I believe it is going to be ready in a few weeks, however don't quote me on that.
Today's Updates(check post date):
- Finishing up test case code.
- Generated randoms have lower bound bias. Fixing..
- Fixed issue. Was a problem with random value being rounded up which was causing the most probable scenario, id=0 for the probability set not being chosen.
- Finding optimal adjustment values..
As you can see below the goal is a curve that can drop quickly but rises slowly.. (see the behavior of the blue line). The gold line is ideal and green is what we currently have. Our current difficulty algorithm is actually on the spot but this is only for case like this where hashpower rises steadily. I'll do some tests with some fringe cases (like the one our network is currently experiencing).
- Signing off.. 8:18PM doing fringe test cases tomorrow/also need to check for timing attack parameters
Thanks MicroGuy; I've gotten as far as I can with trying to load the test client after using the config file.
The error I received was: 'Failed to open mempool file from disk. Continuing anyway.'
I tried to copy the mempool.dat file over to the testnet folder, but am now stuck with the Gui screen of 'Loading the Wallet' and my testnet debug.log files shows 'Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired'
So I'm currently stuck at the moment unable to proceed. I'll keep looking for fixes, but the closest thing I could find was a bug from the bitcoin core wallet with the same issue - https://github.com/bitcoin/bitcoin/pull/9813
If anyone has ideas, let me know.
CreateNewBlock(): total size 1000
Flushing wallet.dat
Flushed wallet.dat 101ms
BitcoinMiner:
proof-of-work found
hash: 000006fd4bb5564dc4c50486c49a17e2fe0ca48bf87076f832c1d60d026f77db
target: 00000fffff000000000000000000000000000000000000000000000000000000
CBlock(hash=1c97479c43e8435cd7d9, PoW=000006fd4bb5564dc4c5, ver=1, hashPrevBlock=63ee26429068a53a39ab, hashMerkleRoot=b7704b3163, nTime=1514879863, nBits=1e0fffff, nNonce=281018368, vtx=1)
CTransaction(hash=b7704b3163, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 04773b4b5a0101062f503253482f)
CTxOut(nValue=10000.00000000, scriptPubKey=0368d568ccf557c37da15707c13f88)
vMerkleTree: b7704b3163
generated 10000.00
keypool keep 3
AddToWallet b7704b3163 new
NotifyTransactionChanged b7704b3163a82e8070504de919cec88cf05df23642e7f9fa76f69668b41cf3e7 status=0
updateWallet b7704b3163a82e8070504de919cec88cf05df23642e7f9fa76f69668b41cf3e7 0
SetBestChain: new best=1c97479c43e8435cd7d9 height=1 work=2097169 date=01/02/2018 07:57:43
ProcessBlock: ACCEPTED
inWallet=1 inModel=0 Index=0-0 showTransaction=0 derivedStatus=0
keypool added key 104, size=101
keypool reserve 4BitcoinMiner:
proof-of-work found
hash: 00000471ccf65cb3da55115040fbb62d75cb630832956beb48d854fb05de927c
target: 000007d798000000000000000000000000000000000000000000000000000000
CBlock(hash=6fb412e64413e4d82028, PoW=00000471ccf65cb3da55, ver=1, hashPrevBlock=48b0f33bc7ef7833b41f, hashMerkleRoot=0f10785710, nTime=1515230274, nBits=1e07d798, nNonce=443744384, vtx=1)
CTransaction(hash=0f10785710, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 044294505a0104062f503253482f)
CTxOut(nValue=1000.00000000, scriptPubKey=03486979745564f5e0f826c2f3b083)
vMerkleTree: 0f10785710
generated 1000.00
keypool keep 473
Local has found possible valid block... queueing until timestamp is valid
Flushing wallet.dat
I ve downloaded the 14.2 version, then i added the conf file to the windows folder which included the wallet.dat file, then the icon turned into green, which indicates the testnet
