node-cryptonote-pool icon indicating copy to clipboard operation
node-cryptonote-pool copied to clipboard

Payments issue - Wrong amount

Open gjnardoni opened this issue 8 years ago • 6 comments

Hello. I've setted up a pool and everything is working fine but payments to miners saying "Wrong amount" on looger.- The currency parameters are:

8 decimals (min units per coin) the max coin emmited are cryptonote "standard" ((uint64_t)(-1)) 2017-07-03 10:26:09 [payments] Error with transfer RPC request to wallet daemon {"code":-4,"message":"Wrong amount"} 2017-07-03 10:26:09 [payments] Payments failed to send to {"amount":241362000000000,"address":"auc146AdaMKeXpQHyX3UeFBqZYM2nqw12eKGUuXAJ1b6K8k4XbYMeRDTCWowNPwai4VEyWM2onLQkdoryRsKaoG35hB8wscNaJ"} 2017-07-03 10:26:09 [payments] Payments splintered and 0 successfully sent, 1 failed

I think it is something related to ./lib/paymentProcessor.js but I don't think where to find exactly.

Could you please lend me a hand?

gjnardoni avatar Jul 03 '17 20:07 gjnardoni

same problem here . . .

2017-07-16 03:55:12 [api] Stat collection finished: 3 ms redis, 4 ms daemon 2017-07-16 03:55:12 [api] Broadcasting to 2 visitors and 0 address lookups 2017-07-16 03:55:17 [api] Stat collection finished: 5 ms redis, 7 ms daemon 2017-07-16 03:55:17 [api] Broadcasting to 2 visitors and 0 address lookups 2017-07-16 03:55:22 [api] Stat collection finished: 2 ms redis, 9 ms daemon 2017-07-16 03:55:22 [api] Broadcasting to 2 visitors and 0 address lookups 2017-07-16 03:55:26 [payments] Error with transfer RPC request to wallet daemon {"code":-4,"message":"Wrong amount"} 2017-07-16 03:55:26 [payments] Payments failed to send to {"amount":60424000000,"address":"fySzv5sbGEMRbZ5EcVKQeyF19Qntga4L9Fg8dnUetd3X67T9oDt89Z1AiPWhGZ7x3R3wMxsuh7Kcaa29WyxetAGg1yZg5LCBB"} { amount: 30212000000, address: 'fySZT9LhZLbh1yQHymMjSNZfNMz8M2PUjfCB8rsDH2c64Zsx1jZgQFv8B1AtqNQTt6PL31YoCQFFUP4gVUkMUZhT11Rsu28LJ' } 2017-07-16 03:55:26 [payments] Payments splintered and 0 successfully sent, 1 failed 2017-07-16 03:55:26 [unlocker] No pending blocks are unlocked yet (1 pending) 2017-07-16 03:55:27 [api] Stat collection finished: 3 ms redis, 4 ms daemon 2017-07-16 03:55:27 [api] Broadcasting to 2 visitors and 0 address lookups 2017-07-16 03:55:32 [api] Stat collection finished: 3 ms redis, 5 ms daemon 2017-07-16 03:55:32 [api] Broadcasting to 2 visitors and 0 address lookups 2017-07-16 03:55:37 [api] Stat collection finished: 3 ms redis, 5 ms daemon 2017-07-16 03:55:37 [api] Broadcasting to 2 visitors and 0 address lookups

any news?

waxcoin avatar Jul 16 '17 00:07 waxcoin

@gjnardoni what configutration did you do, for getting payments, pool keep saying "no worker's balance reached the minimum payment", even being a low value to minimum, any help or advice

freemanjackal avatar Sep 07 '17 21:09 freemanjackal

If you didn't figure it out... I have a solution...

simulanics avatar Mar 17 '18 00:03 simulanics

@simulanics could you please post your solution?

madradio avatar Mar 19 '18 19:03 madradio

This portion of the config is for a pool with a coin that accounts for 8 decimal places ***

    "varDiff": {
        "minDiff": 2,
        "maxDiff": 100000,
        "targetTime": 240, //MUST be set to your block unlock time
        "retargetTime": 120, //Should be, but doesn't have to be, 1/2 to a 1/4 your unlock time.
        "variancePercent": 30,
        "maxJump": 100
    }
},

"payments": {
    "enabled": true,
    "interval": 300,
    "maxAddresses": 50,
    "mixin": 0, //New Pools must set to 0 initially.
    "transferFee": 1000000,
    "minPayment": 100000000, //1.00000000
    "denomination": 1000000 //0.01000000
},

***I only included the portion of the settings that is preventing your pool from working.

If you need direct help, let me know and I can pre-configure all the settings for you to match your coin so that you can compare and see where the slip up occurred. As long as you have source from the working pool sources, you should not have an issue. If it's a bum source, I'll be glad to direct you to a valid one. ***Remember in open source there's a million copies, all different floating around. Thus why I've re-written our crypto's GUI and a majority of crypto code from scratch (to eliminate all the bugs from past developers)....still fully cryptonote compatible though :-) The GUI will be being released for all cryptonote and forknote coins. If you need anything at all, just let me know!

simulanics avatar Jun 26 '18 00:06 simulanics

The issue:

***Wrong amount: Your pool fee + the transaction amount are more than you contain in your wallet.

simulanics avatar Jun 26 '18 00:06 simulanics