Closed verabehr closed 4 months ago
This error is caused by pruning from RPC providers. As the chain progresses, the original block height we chose as a reference is getting older and older. We encountered this issue on test net as well, it looks like at least Liquify has now pruned the block height used for BNB.
I see three ways to improve this atm:
thanks @byte-bandit when does this block-hash check happen? Only at certain times, e.g. whenever pigeon is (re)started?
Every time Pigeon needs to update its chain client configuration, that is usually
Got it, thanks. I'm wondering how many other rpc providers prune. I'm thinking this could become an issue during the next chain upgrade in case folks restart their pigeon - cc @taariq
For now, I'll bring back our validator with a fallback RPC
Agreed. I'm thinking we should go down the road of this automated height/hash maintenance. I think it wouldn't take longer than 1-2 days to implement.
yes, that makes the most sense to me as well. Will open up a new ticket for that
We're getting the following errors on pigeon on the mainnet validator:
This started coincidently? pretty much exactly when I failed over to the quicknode endpoint, by adding a line in the .pigeon/env.sh file with the quicknode endpoint and adding a
#
in front of the line with the liquify endpoint. pigeon service was restarted, no other files or configs were touched. Also tried to undo my changes, but the error persists so I added them back in.Here is a fuller error log that includes both errors