unomp / node-merged-pool Goto Github PK

Hi Guys,

is there any chance to use Siacoin with UNOMP?

Siacoin uses blake2b algorithm.

Any experiences for blake2b?

Thanks

Close this. Posted in wrong location

i was try to setup a pool for XZC
i got this error in debug.log:

2017-02-10 01:59:52 ThreadRPCServer method=submitblock
2017-02-10 01:59:52 ERROR: CTransaction::CheckTransaction() : founders reward missing
2017-02-10 01:59:52 ERROR: CheckBlock() : CheckTransaction failed

how to fix it?
thx

Hey buddy,

How to configure UNOMP with Merged mining?
Thanks in advance!

Hello, could anyone help me to configure node-merged-pool and what are the requirements to install on ubuntu 14.04?

I have tried the following:

Apt-get install build-essential libtool autotools-dev autoconf pkg-config libssl-dev

Apt-get install libboost-all-dev git npm nodejs nodejs-legacy libminiupnpc-dev redis-server

Add-apt-repository ppa: bitcoin / bitcoin

Apt-get update
Apt-get install libdb4.8-dev libdb4.8 ++ - dev
Curl https://raw.githubusercontent.com/creationix/nvm/v0.16.1/install.sh | Sh
Source ~ / .profile
Nvm install 0.12
Nvm use 0.12

Git clone https://github.com/UNOMP/node-merged-pool/

Cd node-merged-pool /

Npm update

Then I tried to set up the example.js file
According to the two scrypt coins that I want to mine in a fused way, changing the rcp ports, username, password, names, symbols to each daemon respectively,
I have replaced the demon wallet of the main currency.
I have adjusted the difficulty of the ports,
But I do not know where else to configure. Or if I lack any dependency
`When I start
Node example.js
Tells me that there is an error, and is that there is no instruction here that says how to use this merged mining module

When it says that I have to create the settings for each currency, this must be done in the same file example.js ?, since I do not see any folder that says coins, it should be renamed to file example.js if that is exactly why?
And also I came up with a doubt I saw in file example.js the following:

Data object contains:
    Job: 4, // job job ID stratum
    Ip: '71 .33.19.37 ', // client IP address
    Port: 3333, // the client port
    Worker: // name of worker stratum 'matt.worker1'
    Height: 443 795, // block height
    BlockReward: 5000000000, // the number of satoshis received as payment for the solution of this block
    Difficulty: 64, // difficulty worker stratum
    ShareDiff: 78, // actual quota difficulty
    BlockDiff: 3349, // difficulty block set for quota fill
    BlockDiffActual: 3349 // actual difficulty for this block
    // Also known as the block solution - set whether the block was found
    BlockHash: '110c0447171ad819dd181216d5d80f41e9218e25d833a2789cb8ba289a52eee4',
    // Exists if "emitInvalidBlockHashes" has the true value
    BlockHashInvalid: '110c0447171ad819dd181216d5d80f41e9218e25d833a2789cb8ba289a52eee4'
    // TxHash is the hash coinbase transaction of the block
    TxHash: '41bb22d6cc409f9c0bae2c39cecd2b3e3e1be213754f23d12c5d6d2003d59b1d,
    Error: "low difficulty quota '// sets whether the quota is rejected for some reason

Do you have to configure something here? For example the IP, would the public IP of my server?
The name of the worker?
Block height

This here
 Difficulty: 64, // difficulty worker stratum
    ShareDiff: 78, // actual quota difficulty
    BlockDiff: 3349, // difficulty block set for quota fill
    BlockDiffActual: 3349 // actual difficulty for this block
    // Also known as the block solution - set whether the block was found
    BlockHash: '110c0447171ad819dd181216d5d80f41e9218e25d833a2789cb8ba289a52eee4',
    // Exists if "emitInvalidBlockHashes" has the true value
    BlockHashInvalid: '110c0447171ad819dd181216d5d80f41e9218e25d833a2789cb8ba289a52eee4'
    // TxHash is the hash coinbase transaction of the block
    TxHash: '41bb22d6cc409f9c0bae2c39cecd2b3e3e1be213754f23d12c5d6d2003d59b1d,
    Error: "low difficulty quota '// sets whether the quota is rejected for some reason

I've setup digibyte myriad groestl algorithm for POOL.
also, changed to support myr-groestl hashing.

changed things:
multi-hashing support myr-groestl for digibyte.
getinfo api -> getblockchaininfo() , getnetworkinfo() , ...
for interfacing with digibyte latest daemon.
adds algoProperties.js to support myr-groestl
procedure to produce.
There's several days of mining. finally I found 3 blocks.
but, NOMP said
"(Thread 4) We thought a block was found but it was rejected by the daemon, share data: {"job":"a8d","ip":"18x.x.x.64","port":3270,"worker":"D8xq5XPZKAYMQ-----------------------,"height":6260408,"blockReward":79656798873,"difficulty":32,"shareDiff":"362533.21566225","blockDiff":314672.733261021,"blockDiffActual":314672.733261021,"blockHash":"0000000000002e46eb5923a74fe9150834595ead2c891364b2b0e673f02ba2f6"}
2018-03-17 04:47:41 [Pool] [digibyte-groestl] (Thread 4) Share accepted at diff 32/362533.21566225 by D8xq5XPZKAYMQC314V5z-------------- [x.x.x.x]
"

I don't know , why this happen, and digibyte daemon logs says nothing.

ambiguity points
I also need to change node-stratum on jobManager.js

for groestlmyriad ?
following is original code of node-stratum

    var coinbaseHasher = (function(){
        switch(options.coin.algorithm){
            case 'keccak':
            case 'blake':
            case 'fugue':
            case 'groestl':
                if (options.coin.normalHashing === true)
                    return util.sha256d;
                else
                    return util.sha256;
            default:
                return util.sha256d;
        }
    })();

setup what I tested.
coins/digibyte.groestl.conf

{
    "name": "digibyte-groestl",
    "symbol": "DGB",
    "algorithm": "groestlmyriad"
}

pool_configs/digibyte.conf

{
    "enabled": true,
    "coin": "digibyte.groestl.json",

    ....

    "daemons": [
        {
            "host": "127.0.0.1",
            "port": 14022,
            "user": "no---",
            "password": "D5wwk5kzlQSdCHi------------------p"
        }
    ],

    "p2p": {
        "enabled": true,
        "host": "127.0.0.1",
        "port": 12024,
        "disableTransactions": false
    },

digibyte daemon configuration.

rpcport=14022
port=12024
daemon=1
listen=1
server=1
algo=groestl
rpcworkqueue=32

blocknotify=/home/nomp/nomp/nodeomp/scripts/blocknotify 127.0.0.1:17117 digibyte-groestl %s

Hi All,

This is my config file:

{
"enabled": true,
"coin": "nova.json",

   "auxes":  {
        "coin": "Scorecoin.json",
        "daemons": [ 
            {
                "host": "127.0.0.1",
                "port": 2002,
                "user": "score",
                "password":

"71RFk6gTZh6oKXWNa6BbhoMEWseP2D9DJLpU5Go5R2xe"
}
]
}

,
"address": "4WHsPXfU6Q8SPrm2zwNzJTwkdQRKvAxUgL",

"rewardRecipients": {
    "": 0.0,
    "": 0.0
},

"paymentProcessing": {
    "enabled": false,
    "paymentInterval": 1800,
    "minimumPayment": 1,
    "daemon": {
        "host": "127.0.0.1",
        "port": 8344,
        "user": "novacoin",
        "password": "testpass"
    }
},

"ports": {
    "5000": {
        "diff": 6024
    },
    "4444": {
        "diff": 46048,
        "varDiff": {
            "minDiff": 46048,
            "maxDiff": 131072,
            "targetTime": 15,
            "retargetTime": 90,
            "variancePercent": 30
        }
    },
    "3100": {
        "diff": 162768
    }
},

"daemons": [
    {
        "host": "127.0.0.1",
        "port": 8344,
        "user": "novacoin",
        "password": "testpass"
    }
],

"p2p": {
    "enabled": false,
    "host": "127.0.0.1",
    "port": 19333,
    "disableTransactions": false
},

"mposMode": {
    "enabled": true,
    "host": "127.0.0.1",
    "port": 3306,
    "user": "root",
    "password": "password",
    "database": "nova33",
    "checkPassword": false,
    "autoCreateWorker": false
}

}

Can anyone help with this subject.
Thanks
Jamie

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Hey, Is there a simple way to get Phi2 algo added to this?

Not sure if this hashing module helps with that process: https://github.com/kimkkikki/phi2_hashing_module

Thanks!

Dev,

do we have Xevan algorithm support also ? For pool functionality

Master bitsend Cannot run a pool for unsupported algorithm "xevan"

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Currently shares from the POW/POS coins main chain when submitted to an auxpow coin as a block, it returns ReadCompactSize() : size too large. I'm guessing that block headers need to be adjusted for the hybrid coin, to be able to submit the block to the AUX network successfully.

I've figured out how to run both daemons and how to adjust my configuration but I'm confused about what address to configure. I put in my Litecoin address and have been mining Litecoin for a while.

Where should I put my Dogecoin address for merge mining?

Not sure if this is the right way to ask this question. Just confused on how the address argument works when merge mining. Any help would be appreciated.