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

APM cannot connect issue #359

Open
IsmaelAznarCarmona opened this issue Dec 3, 2021 · 1 comment
Open

APM cannot connect issue #359

IsmaelAznarCarmona opened this issue Dec 3, 2021 · 1 comment
Assignees
Labels
apm bug Something isn't working prio:medium

Comments

@IsmaelAznarCarmona
Copy link

This is Chuck , discord user, improve idea.

Sometimes when APM cannot connect to BTCSQ-wallet it will cause an issue.
For example if APM is not connected to BTCSQ-wallet for 2-3 hours and then suddenly gets the connection back it will try to endorse all the blocks what it missed in that period of time. Then the endorsment is late and rewards wont be paid.
Also it will cause issue that you wont get any rewards for hours until mempool clears up you have spent VBK for nothing.

@Warchant Warchant added apm bug Something isn't working labels Dec 6, 2021
@Warchant Warchant moved this to Triaged in Proof-of-Proof Dec 6, 2021
@Leonardiae
Copy link

When you start BTCSQ after a while again then the APM auto mines all new blocks which were found since BTCSQ was closed.

However I think for the APM there is no way to know if this were just x new blocks found in the last second or that BTCSQ was just started again. Only way I know of to recognise this is if in Getblockchaininfo initialblockdownload = true, but this is only true when you sync for the first time or very far behind. I tried with ~15 blocks behind and then it's just false like it always is.

@Warchant Warchant moved this from Triaged to Backlog in Proof-of-Proof Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apm bug Something isn't working prio:medium
Projects
Status: Backlog
Development

No branches or pull requests

4 participants