Bounty for open source ByteCoin/Monero pool

[zone117x]

Smooth, Lucas said he fixed the compiling issues with node-multi-hashing so give it another try.


Also regarding the payments in coinbase talk. That isn't practical to do with a normal Bitcoin-based pool for a few reasons - and there are even more reasons why its not practical to do with this new cryptocurrency. Its what p2pool does and it's part of the reason p2pool has its drawbacks compared to a central mining pool.

[mickey_miner]

zone117x,

Regarding the current state of  pool code.  What happens if a block is solved?  Will that be saved to the pool wallet?  I was assuming that the payment processing was still under development but that solved blocks would be on pool wallet.  Is that incorrect? 

[zone117x]

Yes the code is there to submit blocks when found although I haven't been able to test it. Assuming the documentation on bytecoin wiki is correct blocks should be submitted to daemon correctly.

I'm still developing payment processing so I'll have to setup a testnet of sorts somehow to test it all out.

[smooth]

Smooth, Lucas said he fixed the compiling issues with node-multi-hashing so give it another try.


Also regarding the payments in coinbase talk. That isn't practical to do with a normal Bitcoin-based pool for a few reasons - and there are even more reasons why its not practical to do with this new cryptocurrency. Its what p2pool does and it's part of the reason p2pool has its drawbacks compared to a central mining pool.

Eligius does it too right? They don't guarantee it 100% of the time but most payments are made that way.

EDIT: To clarify how this works, the miners who contribute to mining a block don't necessarily get paid from that block, their shares get credited like any other pool and upon reaching a minimum payment threshold their eventual payments are made using some future block's coinbase. That avoids the issues p2pool has with dust payouts vs. minimum share value.

[mickey_miner]

Yes the code is there to submit blocks when found although I haven't been able to test it. Assuming the documentation on bytecoin wiki is correct blocks should be submitted to daemon correctly.

I'm still developing payment processing so I'll have to setup a testnet of sorts somehow to test it all out.

Thanks.  I'm running the pool as is already but with little hashrate.  Miners show shares submitted successfully, Pool shows shares accepted.  No errors.  Guess will have to find block to know everything works for sure.   

Great work so far.  Looking forward to what is still to come.

[zone117x]

Eligius does it too right? They don't guarantee it 100% of the time but most payments are made that way.

EDIT: To clarify how this works, the miners who contribute to mining a block don't necessarily get paid from that block, their shares get credited like any other pool and upon reaching a minimum payment threshold their eventual payments are made using some future block's coinbase. That avoids the issues p2pool has with dust payouts vs. minimum share value.

Right - that works for big pools that find blocks often. If you aren't a huge pool then payment variance (or just payment waiting period) would not make miners happy :p


Latest code should be working very well with vardiff and share acceptance.

Payment processing and IP banning to mitigate low-diff share attacks is under development. Right now I'm stuck on getting address validation. Looks like it should be: slice off 4 byte checksum -> decode rest as varint -> keccak (w/ 64 byte output ??) -> compare result to checksum.

[33zer0w0lf]

Eligius does it too right? They don't guarantee it 100% of the time but most payments are made that way.

EDIT: To clarify how this works, the miners who contribute to mining a block don't necessarily get paid from that block, their shares get credited like any other pool and upon reaching a minimum payment threshold their eventual payments are made using some future block's coinbase. That avoids the issues p2pool has with dust payouts vs. minimum share value.

Right - that works for big pools that find blocks often. If you aren't a huge pool then payment variance (or just payment waiting period) would not make miners happy :p


Latest code should be working very well with vardiff and share acceptance.

Payment processing and IP banning to mitigate low-diff share attacks is under development. Right now I'm stuck on getting address validation. Looks like it should be: slice off 4 byte checksum -> decode rest as varint -> keccak (w/ 64 byte output ??) -> compare result to checksum.

do you have instructions on how to use your pool anywhere?

[smooth]

Eligius does it too right? They don't guarantee it 100% of the time but most payments are made that way.

EDIT: To clarify how this works, the miners who contribute to mining a block don't necessarily get paid from that block, their shares get credited like any other pool and upon reaching a minimum payment threshold their eventual payments are made using some future block's coinbase. That avoids the issues p2pool has with dust payouts vs. minimum share value.

Right - that works for big pools that find blocks often. If you aren't a huge pool then payment variance (or just payment waiting period) would not make miners happy :p

Well as I said even eligius doesn't guarantee all payouts to be done that way. You could just make a regular payout if you go too long in between blocks. 

Of course if the pool isn't finding blocks then you aren't going to be making payouts period (unless PPS).

[perl]

I work for use your code .

Actualy the code can not make more transaction of number processeur .

If fix and make 200 thread.
I get template block 200 per 10 secondes ( each thread get new template )
I have use base58 for valide address .

Actualy the last probleme for make pool is
1.)  very much number of thread without get template block  per thread
2.) RPC send payou
3.) RPC Balance
4.) RPC Find block and amount in block

I can push my code for you if you want.
I have very low change on your code .

monero:shares -> I have add KEY redis for stock share other form
I use scrpt python for get hasrate with redis "LPOP monero:shares"  return json of each share.
Add information of share in base mysql .





 


 

[dreamspark]

Eligius does it too right? They don't guarantee it 100% of the time but most payments are made that way.

EDIT: To clarify how this works, the miners who contribute to mining a block don't necessarily get paid from that block, their shares get credited like any other pool and upon reaching a minimum payment threshold their eventual payments are made using some future block's coinbase. That avoids the issues p2pool has with dust payouts vs. minimum share value.

Right - that works for big pools that find blocks often. If you aren't a huge pool then payment variance (or just payment waiting period) would not make miners happy :p


Latest code should be working very well with vardiff and share acceptance.

Payment processing and IP banning to mitigate low-diff share attacks is under development. Right now I'm stuck on getting address validation. Looks like it should be: slice off 4 byte checksum -> decode rest as varint -> keccak (w/ 64 byte output ??) -> compare result to checksum.

do you have instructions on how to use your pool anywhere?

The usage instructions are on git hub.

[smooth]

Smooth, Lucas said he fixed the compiling issues with node-multi-hashing so give it another try.

I started with a clean new Ubuntu 13.10 install and followed the directions very carefully, with the same result:

Code:

npm http 404 https://registry.npmjs.org/multi-hashing/0.0.8
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-20-generic

Something does not appear to be working on Ubuntu 13.10. What OS are other people using?

[33zer0w0lf]

Eligius does it too right? They don't guarantee it 100% of the time but most payments are made that way.

EDIT: To clarify how this works, the miners who contribute to mining a block don't necessarily get paid from that block, their shares get credited like any other pool and upon reaching a minimum payment threshold their eventual payments are made using some future block's coinbase. That avoids the issues p2pool has with dust payouts vs. minimum share value.

Right - that works for big pools that find blocks often. If you aren't a huge pool then payment variance (or just payment waiting period) would not make miners happy :p


Latest code should be working very well with vardiff and share acceptance.

Payment processing and IP banning to mitigate low-diff share attacks is under development. Right now I'm stuck on getting address validation. Looks like it should be: slice off 4 byte checksum -> decode rest as varint -> keccak (w/ 64 byte output ??) -> compare result to checksum.

do you have instructions on how to use your pool anywhere?

The usage instructions are on git hub.

thank you very helpful, by chance can you please be more specific?

[surfer43]

Eligius does it too right? They don't guarantee it 100% of the time but most payments are made that way.

EDIT: To clarify how this works, the miners who contribute to mining a block don't necessarily get paid from that block, their shares get credited like any other pool and upon reaching a minimum payment threshold their eventual payments are made using some future block's coinbase. That avoids the issues p2pool has with dust payouts vs. minimum share value.

Right - that works for big pools that find blocks often. If you aren't a huge pool then payment variance (or just payment waiting period) would not make miners happy :p


Latest code should be working very well with vardiff and share acceptance.

Payment processing and IP banning to mitigate low-diff share attacks is under development. Right now I'm stuck on getting address validation. Looks like it should be: slice off 4 byte checksum -> decode rest as varint -> keccak (w/ 64 byte output ??) -> compare result to checksum.

do you have instructions on how to use your pool anywhere?

The usage instructions are on git hub.

thank you very helpful, by chance can you please be more specific?

https://github.com/zone117x/node-cryptonote-pool
Just scroll down for the instructions. They're in README.md.

[smooth]

1000 MRO

NOT received

[33zer0w0lf]

Eligius does it too right? They don't guarantee it 100% of the time but most payments are made that way.

EDIT: To clarify how this works, the miners who contribute to mining a block don't necessarily get paid from that block, their shares get credited like any other pool and upon reaching a minimum payment threshold their eventual payments are made using some future block's coinbase. That avoids the issues p2pool has with dust payouts vs. minimum share value.

Right - that works for big pools that find blocks often. If you aren't a huge pool then payment variance (or just payment waiting period) would not make miners happy :p


Latest code should be working very well with vardiff and share acceptance.

Payment processing and IP banning to mitigate low-diff share attacks is under development. Right now I'm stuck on getting address validation. Looks like it should be: slice off 4 byte checksum -> decode rest as varint -> keccak (w/ 64 byte output ??) -> compare result to checksum.

do you have instructions on how to use your pool anywhere?

The usage instructions are on git hub.

thank you very helpful, by chance can you please be more specific?

https://github.com/zone117x/node-cryptonote-pool
Just scroll down for the instructions. They're in README.md.

these instructions are to setup your own pool aren't they?

[surfer43]

these instructions are to setup your own pool aren't they?

Yeah. Once the pool is finished all you have to do is download a cpuminer for cryptonight or maybe simpleminer and point it to a pool. All zone117x is doing is creating the pool software. Anyone will be able to set up a pool after it's complete.

[superresistant]

1000 MRO

NOT received

 

[33zer0w0lf]

these instructions are to setup your own pool aren't they?

Yeah. Once the pool is finished all you have to do is download a cpuminer for cryptonight or maybe simpleminer and point it to a pool. All zone117x is doing is creating the pool software. Anyone will be able to set up a pool after it's complete.

ahhh  gotcha, isn't achtit setting up a pool?

[surfer43]

these instructions are to setup your own pool aren't they?

Yeah. Once the pool is finished all you have to do is download a cpuminer for cryptonight or maybe simpleminer and point it to a pool. All zone117x is doing is creating the pool software. Anyone will be able to set up a pool after it's complete.

ahhh  gotcha, isn't achtit setting up a pool?

Archit is creating a competing pool software.

[mickey_miner]

Smooth, Lucas said he fixed the compiling issues with node-multi-hashing so give it another try.

I started with a clean new Ubuntu 13.10 install and followed the directions very carefully, with the same result:

Code:

npm http 404 https://registry.npmjs.org/multi-hashing/0.0.8
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-20-generic

Something does not appear to be working on Ubuntu 13.10. What OS are other people using?

I have it working on 13.10. 

I had problems when I installed node.js using "sudo apt-get install nodejs"  So I tried building from source:

sudo apt-get install python g++ make checkinstall fakeroot
src=$(mktemp -d) && cd $src
wget -N http://nodejs.org/dist/node-latest.tar.gz
tar xzvf node-latest.tar.gz && cd node-v*
./configure
sudo fakeroot checkinstall -y --install=no --pkgversion $(echo $(pwd) | sed -n -re's/.+node-v(.+)$/\1/p') make -j$(($(nproc)+1)) install
sudo dpkg -i node_*


And it worked after that.  The github instructions for Debian/LMDE work for Ubuntu 13.10. 

I just tried it on another 13.10 and it worked building from source.

Here is the result after running node init.js to start pool:

2014-05-13 17:27:03 [Master]    [Pool Spawner] Spawned pool on 1 thread(s)
2014-05-13 17:27:03 [Pool]      (Thread 1) [Job Refresher] Found new block at height 38161 w/ difficulty of 12035864
2014-05-13 17:27:03 [Pool]      (Thread 1) [Server] Started server listening on port 5555