Bounty for open source ByteCoin/Monero pool

[archit]

It's up again, at least for now

[zone117x]

https://github.com/zone117x/node-cryptonote-pool

Stuff that is working:

• Share validation
• Node.js clustering for pool performance
• Variable difficulty
• Long polling
• Configurable pool difficulty and vardiff
• Detailed logging with configurable log levels (debug, warn, error) and colorful log styling
• Storing shares in redis per miner
• Storing hashrate data
• Submitting and recording solved blocks
• Misc. configurable options: worker timeouts, block polling interval, pool threads
• Documentation (installation and usage instructions)

Stuff that is left:

• Payment processor (checks for confirmed blocks then payouts according to shares)
• AJAX/REST API to display stats (hashrates, payouts, coin network info, etc)
• Light-weight front-end which uses API to display stats

The stuff left are the easy parts. ETA for all of the above is 24-48 hours of this point.


Feel free to test it out: https://github.com/zone117x/node-cryptonote-pool#usage

[surfer43]

https://github.com/zone117x/node-cryptonote-pool

Stuff that is working:

• Share validation
• Node.js clustering for pool performance
• Variable difficulty
• Long polling
• Configurable pool difficulty and vardiff
• Detailed logging with configurable log levels (debug, warn, error) and colorful log styling
• Storing shares in redis per miner
• Storing hashrate data
• Submitting and recording solved blocks
• Misc. configurable options: worker timeouts, block polling interval, pool threads
• Documentation (installation and usage instructions)

Stuff that is left:

• Payment processor (checks for confirmed blocks then payouts according to shares)
• AJAX/REST API to display stats (hashrates, payouts, coin network info, etc)
• Light-weight front-end which uses API to display stats

The stuff left are the easy parts. ETA for all of the above is 24-48 hours of this point.


Feel free to test it out: https://github.com/zone117x/node-cryptonote-pool#usage

Nice! Works great. 

A pool will be ready as soon as you're done. 

[smooth]

Feel free to test it out: https://github.com/zone117x/node-cryptonote-pool#usage

I get some errors at the npm update stage on Ubuntu 13.10

I installed node using

Code:

sudo apt-get install nodejs npm

Code:

npm ERR! Error: version not found: 0.0.8 : multi-hashing/0.0.8
npm ERR!     at RegClient.<anonymous> (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:269:14)
npm ERR!     at Request.self.callback (/usr/lib/nodejs/request/main.js:119:22)
npm ERR!     at Request.<anonymous> (/usr/lib/nodejs/request/main.js:525:16)
npm ERR!     at Request.EventEmitter.emit (events.js:95:17)
npm ERR!     at IncomingMessage.<anonymous> (/usr/lib/nodejs/request/main.js:484:14)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:910:16
npm ERR!     at process._tickCallback (node.js:415:13)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://bugs.debian.org/npm>
npm ERR! or use
npm ERR!     reportbug --attach /home/ubuntu/pool/npm-debug.log npm

Then later

Code:

npm http 200 https://registry.npmjs.org/nan/-/nan-1.0.0.tgz

> bignum@0.7.0 install /home/ubuntu/pool/node_modules/bignum
> node-gyp configure build

/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:789:12)
gyp ERR! System Linux 3.11.0-14-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "configure" "build"
gyp ERR! cwd /home/ubuntu/pool/node_modules/bignum
gyp ERR! node -v v0.10.15
gyp ERR! node-gyp -v v0.10.9
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian
 
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ubuntu/pool/npm-debug.log
npm ERR! not ok code 0

[zone117x]

Smooth - looks like your system is lacking ability to compile the C modules. You need some dependencies installed.

From https://www.npmjs.org/package/node-gyp

On Unix:
python (v2.7 recommended, v3.x.x is not supported)
make
A proper C/C++ compiler toolchain, like GCC

[smooth]

Smooth - looks like your system is lacking ability to compile the C modules. You need some dependencies installed.

That is odd. I have gcc, g++, and python. 

The gcc stuff I assume came with build-essential, which was already installed before I started.

From https://www.npmjs.org/package/node-gyp

On Unix:
python (v2.7 recommended, v3.x.x is not supported)
make
A proper C/C++ compiler toolchain, like GCC

[smooth]

I think the above problem is due to this:

nodejs command
--------------

The upstream name for the Node.js interpreter command is "node".
In Debian the interpreter command has been changed to "nodejs".

This was done to prevent a namespace collision: other commands use
the same name in their upstreams, such as ax25-node from the "node"
package.

Scripts calling Node.js as a shell command must be changed to instead
use the "nodejs" command.
/usr/share/doc/nodejs/README.Debian (END)

Not sure how to resolve that though.

[smooth]

Alright I just linked nodejs to /usr/local/bin/node

That seemed to fix the gyp problem, but I'm still getting this earlier error:

npm ERR! Error: version not found: 0.0.8 : multi-hashing/0.0.8
npm ERR!     at RegClient.<anonymous> (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:269:14)
npm ERR!     at Request.self.callback (/usr/lib/nodejs/request/main.js:119:22)
npm ERR!     at Request.<anonymous> (/usr/lib/nodejs/request/main.js:525:16)
npm ERR!     at Request.EventEmitter.emit (events.js:95:17)
npm ERR!     at IncomingMessage.<anonymous> (/usr/lib/nodejs/request/main.js:484:14)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:910:16
npm ERR!     at process._tickCallback (node.js:415:13)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://bugs.debian.org/npm>
npm ERR! or use
npm ERR!     reportbug --attach /home/ubuntu/pool/npm-debug.log npm

npm ERR! System Linux 3.11.0-14-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "update"
npm ERR! cwd /home/ubuntu/pool
npm ERR! node -v v0.10.15
npm ERR! npm -v 1.2.18

[perl]

Just for test :
62.210.78.186:5555

The connexion of wallet is not possible actualy in version .
xxxxxxx@monero:~# simplewallet  --rpc-bind-ip=127.0.0.1 --rpc-bind-port=8082  --wallet-file=pool
bitmonero wallet v0.8.6.295()
2014-May-12 16:55:08.423056 ERROR /usr/src/bitmonero/src/simplewallet/simplewallet.cpp:980 Wallet password not set.

[perl]

New block drop old jobs and close connexion
2014-05-12 17:15:57 [Pool]      (Thread [Job Refresher] Found new block at height 36523 w/ difficulty of 11032515
2014-May-12 17:15:48.107673 ERROR /src/bitmonero/contrib/epee/include/storages/http_abstract_invoke.h:112 RPC call of "submit" returned error: -1, message: Invalid job id
2014-May-12 17:15:49.135724 ERROR /src/bitmonero/contrib/epee/include/storages/http_abstract_invoke.h:112 RPC call of "getjob" returned error: -1, message: Unauthenticated

[zone117x]

Thanks for the error log perl I'll look into it. Part of the problem is this crappy old get-work like protocol we have to work with.

Smooth someone else said they are having issues getting node-multi-hashing to compile. Not sure why its not working for some people - but I'm looking into it. Also not sure why you had that much trouble getting Node.js working - did you follow these instructions? https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager#ubuntu-mint-elementary-os

Btw my guy looks like he has stratum protocol with cryptonight almost working with CPUMiner: https://github.com/LucasJones/cpuminer-multi/commits/master

Looking like I'll be able to deliver you to you guys not only a pool for simpleminer, but also a stratum pool and cryptonote version of CPUMiner (stratum / multi-core)

 

[zone117x]

https://github.com/zone117x/node-multi-hashing/issues/11

Yeah it appears some compiler(s) have problem with latest node-multi-hashing. It works for me but I'm looking into getting it fixed.

[mickey_miner]

https://github.com/zone117x/node-cryptonote-pool

Stuff that is working:

• Share validation
• Node.js clustering for pool performance
• Variable difficulty
• Long polling
• Configurable pool difficulty and vardiff
• Detailed logging with configurable log levels (debug, warn, error) and colorful log styling
• Storing shares in redis per miner
• Storing hashrate data
• Submitting and recording solved blocks
• Misc. configurable options: worker timeouts, block polling interval, pool threads
• Documentation (installation and usage instructions)

Stuff that is left:

• Payment processor (checks for confirmed blocks then payouts according to shares)
• AJAX/REST API to display stats (hashrates, payouts, coin network info, etc)
• Light-weight front-end which uses API to display stats

The stuff left are the easy parts. ETA for all of the above is 24-48 hours of this point.


Feel free to test it out: https://github.com/zone117x/node-cryptonote-pool#usage

It seems to be working.

From miner:

2014-May-12 12:19:32.355083 Share found: nonce=14000000 for job=963732803333550, submitting...
2014-May-12 12:19:32.908114 READ ENDS: Success. bytes_tr: 196
2014-May-12 12:19:32.915115 -->>http_stream_filter::parse_cached_header(*)
2014-May-12 12:19:32.924115 <<--http_stream_filter::parse_cached_header(*)
2014-May-12 12:19:32.933116 Share submitted successfully!
2014-May-12 12:19:32.939116 Getting next job...

From pool:

2014-05-12 19:06:56 [Pool]      (Thread 4) [Share Validator] Accepted share at difficulty 12/57 from 44MhE4hX58XE4vCEkTbjpsE1EZVW4oQSaAqfwAbo5PufaYMPCSSf2L72bNhMkYzqULKrniDRWt7KCJq QmWVEzxEC4s5yZxz@24.21.52.96
2014-05-12 19:07:03 [Pool]      (Thread 4) [Share Validator] Accepted share at difficulty 8/12 from 44MhE4hX58XE4vCEkTbjpsE1EZVW4oQSaAqfwAbo5PufaYMPCSSf2L72bNhMkYzqULKrniDRWt7KCJq QmWVEzxEC4s5yZxz@24.21.52.96
2014-05-12 19:07:10 [Pool]      (Thread 4) [Share Validator] Accepted share at difficulty 8/36 from 44MhE4hX58XE4vCEkTbjpsE1EZVW4oQSaAqfwAbo5PufaYMPCSSf2L72bNhMkYzqULKrniDRWt7KCJq QmWVEzxEC4s5yZxz@24.21.52.96
2014-05-12 19:07:13 [Pool]      (Thread 4) [Share Validator] Accepted share at difficulty 8/75 from 44MhE4hX58XE4vCEkTbjpsE1EZVW4oQSaAqfwAbo5PufaYMPCSSf2L72bNhMkYzqULKrniDRWt7KCJq QmWVEzxEC4s5yZxz@24.21.52.96
2014-05-12 19:07:15 [Pool]      (Thread 4) [Share Validator] Accepted share at difficulty 8/9 from 44MhE4hX58XE4vCEkTbjpsE1EZVW4oQSaAqfwAbo5PufaYMPCSSf2L72bNhMkYzqULKrniDRWt7KCJq QmWVEzxEC4s5yZxz@24.21.52.96
2014-05-12 19:07:28 [Pool]      (Thread 4) [Difficulty Retargeter] Retargetting difficulty 8 to 19 for 44MhE4hX58XE4vCEkTbjps


Now to point more miners and solve a block.

[smooth]

Smooth someone else said they are having issues getting node-multi-hashing to compile. Not sure why its not working for some people - but I'm looking into it. Also not sure why you had that much trouble getting Node.js working - did you follow these instructions? https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager#ubuntu-mint-elementary-os

Yes I followed those directions. I'll take a look at your follow up post about hashing.

[perl]

It is poosible modified bitminored for add more one transaction of generation ?

I think is more simple and more efficace for make payout if miner is payed direct in the block

[mickey_miner]

So when using simpleminer is this correct command?

./simpleminer --pool-addr=xxx.xxx.xxx.xxxx:5555 --login=wallet_address --pass !


And if my pool solves block will that go directly into pool wallet for now?

[surfer43]

So when using simpleminer is this correct command?

./simpleminer --pool-addr=xxx.xxx.xxx.xxxx:5555 --login=wallet_address --pass !


And if my pool solves block will that go directly into pool wallet for now?

I don't think the pool submits blocks correctly atm. Password can be anything.

[mickey_miner]

So when using simpleminer is this correct command?

./simpleminer --pool-addr=xxx.xxx.xxx.xxxx:5555 --login=wallet_address --pass !


And if my pool solves block will that go directly into pool wallet for now?

I don't think the pool submits blocks correctly atm. Password can be anything.

I'm using pool wallet address.

[smooth]

It is poosible modified bitminored for add more one transaction of generation ?

I think is more simple and more efficace for make payout if miner is payed direct in the block

I would advise caution here. This is a brand new code base and there is no way to know without testing it if all the pieces would handle coinbase payouts correctly. The ill-advised attempt to do merged mining has already broken things twice.

Coinbase payouts are definitely a desirable feature, I'm just advising a yellow light here, not red.

[perl]

You caution is useless .
I do not want to make a change in a dark corner
I preferred and pushes the change is done in the official sources.

Acualy is very hard make payout otherwise coinbase payout