ironfish icon indicating copy to clipboard operation
ironfish copied to clipboard

Published 20 hours ago • verified publisher icon iron-fish

Since 0.1.44 node do not see pool payments

Open gzivdo opened this issue 2 years ago • 3 comments

What happened?

After upgrade every day my nodes do not see pool payments at all. Workaround for now:

  • rescan
  • OR stop node before pool payment made and start after 3h+.
  • OR rollback fs to yesterday (actually 3h+ after payment and rollback to just before payment)

I suppose something wrong with mempool or transaction broadcasting code.

Version

0.1.44

Debug output

No response

Relevant log output

No response

Graffiti

ar2Obyahain

gzivdo avatar Aug 24 '22 08:08 gzivdo

What do you mean by not "seeing" pool payments? You think your account has received payment but isn't updating locally? Or the pool isn't paying you at all?

What is the output of ironfish debug for you?

lwisne avatar Aug 29 '22 19:08 lwisne

Not see locally, it was whole last week on all my nodes, now it almost ok (may be 1 of few nodes not see each day). Same issue had many ppl from local tg chat last week.

Now i have similar issue when i sending from node a to node b, it not see part of transactions, i need to wait about 5h then do "fast" rescan (starting from some block prior account creation). without it, it can stay for a day+ and nothging changes, it see only part of transactions without any "actions". I also know one who do not do rescan for 2 months, after rescan yesterday he found ~200 iron ). Seems that problem depends on current network condition and selected peers condition and some bug in processing mem pool or whatever. The database contains all required transactions, but they not taken into account somehow.

as for debug output, i will do that in the next case. should i also stop node before "debug", wihtout it print same as status.

gzivdo avatar Aug 30 '22 17:08 gzivdo

I see now what you wanted to check in debug, after rescan head is reset, but i supposed that it will be at the highest block in local database. Its affect issue in previous comment, but not to original issue, because node was online without rescan for few days.

gzivdo avatar Aug 30 '22 21:08 gzivdo

Closing this issue since we rewrote a lot of the logic for pool payours in #3353.

Please open a new issue if you're continuing to see problems with pool payouts.

hughy avatar Feb 28 '23 00:02 hughy