dvandal / cryptonote-nodejs-pool

Mining pool for all CryptoNote based coins using Cryptonight, Cryptonight Light and Cryptonight Heavy algorithms
GNU General Public License v2.0
366 stars 611 forks source link

Haven (XHV) payment issue - SOLVED #588

Closed SixLitr closed 4 years ago

SixLitr commented 4 years ago

Has anyone successfully used this repo (recently - it was working fine many months ago) to build a Haven pool that correctly issues payments? The daemon and wallet are sync'd fine, and I can manually make payments from the wallet-cli, but the pool will not initiate a payment automatically. Trying to find error logs and none seem to be helping. Any assistance is appreciated!

muscleman commented 4 years ago

my changes to this software did not change payment implementation in this pool upto and including v2.0.0. eg) has not changed since v1.3

v2.1.0 and above that are not available here do change alot for turtleservice, api payments etc

if the new haven release is available maybe you should contact them at get a fix.

SixLitr commented 4 years ago

The problem seems to lie with a "bad ring size, invalid input" error in the config.json - its a poolside issue. The haven daemon and wallet are up to date and function properly, but the pools rpc commands are not correct. I tried changing the "mixin" value default of 5 to 11, swapping with "ring_size" of 11 (which is correct according to devs) and even using both values and variables at the same time. None of these produce a successful transaction.

SixLitr commented 4 years ago

The problem seems to lie with a "bad ring size, invalid input" error in the config.json - its a poolside issue. The haven daemon and wallet are up to date and function properly, but the pools rpc commands are not correct. I tried changing the "mixin" value default of 5 to 11, swapping with "ring_size" of 11 (which is correct according to devs) and even using both values and variables at the same time. None of these produce a successful transaction.

Found The Problem:

The default config.json uses "mixin": 5,

This needs to be changed to "ringSize": 11,

Note: the issue was using ring_size instead of ringSize - this was changed at some point apparently.

saymissme commented 4 years ago

i use "mixin": 11 not work got this info

{"code":-4,"message":"An output in this transaction was previously spent on another chain with ring size 17, it cannot be spent now with ring size 11 as it is smaller: use a higher ring size"} change mixin to 17 got tx verification failed: bad ring size, invalid input

how to fix it?

saymissme commented 4 years ago

https://github.com/haven-protocol-org/haven-protocol/issues/4

fixed thx

nons-pool commented 4 years ago

does anybody know if it should be ring_size, ringSize, or mixin? Based on the discussion on Haven issue 4, it is a size of 11, but the variable doesn't seem to get passed on to the rpc call. I get errors when paying out with ringSize, but I'm still using the code from before the wipe-out, should I update to the new one?

SixLitr commented 4 years ago

The problem seems to lie with a "bad ring size, invalid input" error in the config.json - its a poolside issue. The haven daemon and wallet are up to date and function properly, but the pools rpc commands are not correct. I tried changing the "mixin" value default of 5 to 11, swapping with "ring_size" of 11 (which is correct according to devs) and even using both values and variables at the same time. None of these produce a successful transaction.

Found The Problem:

The default config.json uses "mixin": 5,

This needs to be changed to "ringSize": 11,

Note: the issue was using ring_size instead of ringSize - this was changed at some point apparently.

Please read above.

nons-pool commented 4 years ago

Thank you for your response, unfortunately ringSize didn't work so it wasn't clear for me. I'm going to look over your fork and see if everything lines up. Maybe I need to delete that shared-ring hidden folder before starting everything again.