Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
cryptonoteminingpool opened this issue Jan 4, 2018 · 17 comments

Comments

@cryptonoteminingpool
Copy link

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
Copy link

Same here
Can someone help?

@flarecurrency
Copy link

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
Copy link

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

@ghost
Copy link

ghost commented Feb 5, 2018

I'm facing the same problem here.

@hoofmen
Copy link

hoofmen commented Feb 8, 2018

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

@pmitchev
Copy link

pmitchev commented Feb 8, 2018

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
Copy link

hoofmen commented Feb 10, 2018

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

@appkoders
Copy link

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

@Masyaua
Copy link

Masyaua commented Feb 16, 2018

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

@blueavenue
Copy link

blueavenue commented Feb 18, 2018

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
Copy link

Masyaua commented Feb 18, 2018

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

@blueavenue
Copy link

blueavenue commented Feb 18, 2018

Yes, why you ask?

Here the module unlocker:

unlocker

@blueavenue
Copy link

blueavenue commented Feb 23, 2018

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
Copy link

@blueavenue

could u explain why?

i changed Mixin and maxTransactionAmount with no effect.

@blueavenue
Copy link

Hello calidion,

what error says the pool log?

Which error shown the pool by running on the server?

@calidion
Copy link

@blueavenue

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

@blueavenue
Copy link

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
},

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants