Raspiblitz: Mempool: Fix order of blocks

Created on 21 Oct 2020 · 7Comments · Source: rootzoll/raspiblitz

see: https://twitter.com/KevinR4v/status/1318732809050226688?s=20

Source

rootzoll

Most helpful comment

okay, thanks for letting us know, I suppose your node was just out of sync because nobody has ever reported this to us before. since it's no longer reproducing i would suggest to close this issue for now, but let us know it happens again

wiz on 21 Oct 2020

👍2

All 7 comments

Check with @wiz what can be changed in the config to fix this.

rootzoll on 21 Oct 2020

@rootzoll are you able to reproduce this issue? I checked your scripts and I don't see anything strange in the configuration that would cause this...

wiz on 21 Oct 2020

Could check if the timestamp of those particular blocks are off and if the sorting is made by time not blockheight: https://twitter.com/openoms/status/1318831664303378432?s=19

EDIT: it is not the timestamps:

deleted the tweet so it does not come across as suggesting mempool.space has a bug.

openoms on 21 Oct 2020

👍2

do you have reason to believe this is a bug in mempool? since nobody has ever reported to us I assume it was just a configuration problem with how raspiblitz is installing mempool. has anyone been able to reproduce the issue since this was reported?

wiz on 21 Oct 2020

I did not see this happen, just trying to guess the cause.

openoms on 21 Oct 2020

I reported this small bug I noticed in the mempoolspace instance running on my raspiblitz, it does not show any incorrect block anymore after running for some hours. So I think it could have been due to the RaspiBlitz beeing offline for a bit whilst upgrading and then immediately after starting mempoolspace service. Showing the blocks in the order the backend could fetch them from the node, and it takes a little while to catch up to the chain tip.