nomp and solo mining

[jjj092353]

is it possible to use nomp with a miner that only support stratum protocol to solo mine?

I have nomp up and runniing fine with Mpos for a few dozen coins, but have one wallet than I installed on the nomp server and want to solo mine into that wallet using the stratum protocol. I setup a .json file with the correct credentials, set

"paymentProcessing": {
"enabled": false,

"mposMode": {
    "enabled": false,

and have the deamon set to connect to the local wallet?

my question is to have have to set worker-name = daemon-user-name and worker-password = deamon-password.

or should I learn how to setup up p2p and mine that way?

[shovelpool]

I think your best bet would be running a non-mpos nomp on a different
server and running with either 100% fees paying to the pool wallet, or zero
% fees paying to the mining configurations address
On Oct 30, 2014 12:06 PM, "jjj092353" notifications@github.com wrote:

is it possible to use nomp with a miner that only support stratum protocol
to solo mine?

I have nomp up and runniing fine with Mpos for a few dozen coins, but have
one wallet than I installed on the nomp server and want to solo mine into
that wallet using the stratum protocol. I setup a .json file with the
correct credentials, set

"paymentProcessing": {
"enabled": false,

"mposMode": {
"enabled": false,

and have the deamon set to connect to the local wallet?

my question is to have have to set worker-name = daemon-user-name and
worker-password = deamon-password.

or should I learn how to setup up p2p and mine that way?

—
Reply to this email directly or view it on GitHub
#406.

[jjj092353]

good idea - my question is in the lack of a mpos/database what username/password to use for worker?

what authorizes the worker?

[sigwo]

You would star the other instance in NOMP mode, not MPOS mode.

On Thursday, October 30, 2014, jjj092353 notifications@github.com wrote:

good idea - my question is in the lack of a mpos/database what
username/password to use for worker?

what authorizes the worker?

—
Reply to this email directly or view it on GitHub
#406 (comment)
.

-Steven

[jjj092353]

I'm not starting the other instance in nomp mode - but my question still remains - what part of nomp authenticates the username and password of the miner? - is it the same username and password used for the coin daemon?

[jjj092353]

by the way what's leading me to this is the addition of a new really fast mining machine - see my issue here: zone117x/nomp-app#2

[sigwo]

The NOMP validates the address of a miner. There is no "authentication" of
the miner.

The wallet is accessed/authenticated by NOMP by the username/password combo
of the daemon.

On Thursday, October 30, 2014, jjj092353 notifications@github.com wrote:

I'm not starting the other instance in nomp mode - but my question still
remains - what part of nomp authenticates the username and password of the
miner? - is it the same username and password used for the coin daemon?

—
Reply to this email directly or view it on GitHub
#406 (comment)
.

-Steven

[jjj092353]

ok - so the username of the miner must be the coin address of the wallet deamon?

[shovelpool]

:

When u get the no-mpos nomp running, the nomp getting started page tells
you exactly how to do it.

Solved blocks get stored in the pool wallet and are then processed out to
the wallet address in the miner config file when they mature.
On Oct 30, 2014 2:38 PM, "jjj092353" notifications@github.com wrote:

good idea - my question is in the lack of a mpos/database what
username/password to use for worker?

what authorizes the worker?

—
Reply to this email directly or view it on GitHub
#406 (comment)
.

[Cryptix23]

""ok - so the username of the miner must be the coin address of the wallet deamon?""

No, the username of the miner MUST be your final wallet address (i.e. where you want to receive your coins).

[mortaca]

You can see my NOMP modificated to solo in solomining.com

[Cryptix23]

nice stuff, please share your modified source code.

[mortaca]

On shareProcessor.js

    if (isValidBlock){
        redisCommands.push(['hincrbyfloat', coin + ':shares:round' + shareData.height, shareData.worker, shareData.difficulty]);
        redisCommands.push(['sadd', coin + ':blocksPending', [shareData.blockHash, shareData.txHash, shareData.height].join(':')]);
        redisCommands.push(['hincrby', coin + ':stats', 'validBlocks', 1]);
    }

[Cryptix23]

Many thanks.