forknote / forknote-pool

Mining pool for Bytecoin/Forknote based coins such as Bytecoin and Dashcoin.
https://github.com/forknote/forknote-pool
GNU General Public License v2.0
123 stars 185 forks source link

Unlocker and Payments module not sending balance and payments to miners? #55

Open cryptonoteminingpool opened 6 years ago

cryptonoteminingpool commented 6 years ago

Hello.

My pool has found a block but the miners have not received any balance or payment.

All of the miners appear with no pending or paid balance, and I can't understand why this hasn't been processed.

The pool info log shows that the block was found: https://snag.gy/HcxiQW.jpg

I have checked in the administration that the balance is already available.

In the unlocker log, I see that the block seems to have been unlocked already: https://snag.gy/bW1Fov.jpg

In the payments log I see messages saying that the payment threshold for the users has not been reached: https://snag.gy/8SKjfT.jpg

I have set in the config file for the pool the minimum values for payment as being 5: https://snag.gy/znVCes.jpg Here is the output I see on the site: https://snag.gy/dcgAaf.jpg

Am I missing something here, or is there anything not working in the payments module?

Thank you.

viktormelnychuk commented 6 years ago

Same here Can someone help?

flarecurrency commented 6 years ago

change in the file lib/blockUnlocker.js rule 48

apiInterfaces.rpcDaemon('getblockheaderbyheight', {height: block.height}, function(error, result){ to;

apiInterfaces.rpcDaemon('getblockheaderbyheight', {height: block.height + 1}, function(error, result){

Close ticket please

appkoders commented 6 years ago

@flarecurrency Can you tell what the change will do? It looks like its the function that checks for orphaned blocks.

ghost commented 6 years ago

I'm facing the same problem here.

hoofmen commented 6 years ago

Exactly the same problem, just tried @flarecurrency suggestion and see no difference so far.

pmitchev commented 6 years ago

Bytecoin moved the start of block counting in v2 from 0 to 1. The change in the pool software is just moving the counter for 0 to 1. In forknote we still use 0 as counter starter. That's why this fix is not implemented as default. The ticked will be closed when the fix is added to default

hoofmen commented 6 years ago

I take it back! It worked for me :-)

appkoders commented 6 years ago

I tried @flarecurrency suggestion and it marked all mined blocks as orphans.

Masyaua commented 6 years ago

Is the problem solved or not? I did not help the unit marked an orphan! thanks for the help

blueavenue commented 6 years ago

I have the same issue. I tried to change the file, but now there is nothing under payment.

My pool log says: issuepool

And my worker is showing this (nothing happend at pending balance since one hour after editing the file BlockUnlocker.js:

issueworker

But all runs, Wallet is okay and all other, look:

issueadmin

Info: I use the CryptoNoteMiner on client.

If i start node init.js my VPS-Server says this:

issuepoolvps

What should i do?

Masyaua commented 6 years ago

blueavenue and you can see your file: BlockUnlocker.js ????

blueavenue commented 6 years ago

Yes, why you ask?

Here the module unlocker:

unlocker

blueavenue commented 6 years ago

I solved it with help from other threads an my try:

If you have errors with payment try this (in pool config.json) Edit Mixin 3 to 1 and set "maxTransactionAmount": 5000000000000,

And i use Ubuntu 14 minimal.

You dont have to edit (this makes errors in blockchain):

apiInterfaces.rpcDaemon('getblockheaderbyheight', {height: block.height + 1}, function(error, result)

calidion commented 6 years ago

@blueavenue

could u explain why?

i changed Mixin and maxTransactionAmount with no effect.

blueavenue commented 6 years ago

Hello calidion,

what error says the pool log?

Which error shown the pool by running on the server?

calidion commented 6 years ago

@blueavenue

it seems due to the lack of the pool balance that the pool will not pay for the miners.

blueavenue commented 6 years ago

But i need to help you the errors listed here or a screenshot from the pool server errors.

There is no lack of the pool balance, if you setup the config.json correctly. What says the admin-panel?

Wallet and Dameon ok status?

You can try this:

The minPayment should smaller then the maxTransactionAmmount. After i while with mining you can change then like this (my config.json):

"payments": {
    "enabled": true,
    "interval": 600,
    "maxAddresses": 50,
    "mixin": 1,
    "transferFee": 50000000,
    "minPayment": 500000000000000,
    "maxTransactionAmount": 0,
    "denomination": 1000000000
},