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

Pools sometimes not paying out found blocks at all #533

Open
kbs1 opened this issue Apr 10, 2019 · 0 comments
Open

Pools sometimes not paying out found blocks at all #533

kbs1 opened this issue Apr 10, 2019 · 0 comments

Comments

@kbs1
Copy link
Contributor

kbs1 commented Apr 10, 2019

While paying out collected fees (used to be ~once a month), I many times noticed that there are leftover unpaid (1024 coins left) main blocks that are of old date (should have been paid out long time ago).

This seems to happen during desyncs, or when the node is "trying to connect to the main network" (see also next bug for more details about this). This also seems to happen on ANY network related errors. We also saw blocks with ~200 balance left or similar. Since there are 10 transfers per generated tx block (in the C code), it seems XDAG doesn't actually check if the tx block generated WAS accepted by the other nodes (on network outages or similar).

So we think that 1024-coin blocks OR blocks with an arbitrary coin amount left are caused by dropped network packets or similar.

So when XDAG generates a block, and "sends it", if this fails, does XDAG check for the failure, and if yes, does it attempt to re-send the generated tx block?

Unfortunately we don't have any logs for these instances, but next time, I will collect them.

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

1 participant