Open aditya-manit opened 2 months ago
In the https://paloma.explorers.guru/block/24036421 block, I see there's a delegation tx https://paloma.explorers.guru/transaction/2897576E27E693DDB30F2427D9AAEDE1B3FACB3ABB1004BA57D5140A1E78F048?height=24036421 from a Paloma Lightnode. it may be related.
We chain halted today after upgrade.
Sep 22 19:32:16 host palomad[2652531]: 7:32PM ERR prevote step: consensus deems this block invalid; prevoting nil err="wrong Block.Header.AppHash. Expected 6F2516BE4832BF4777554CF895D447C181FBB709C3470576F0ED3D443F7E2208, got 7DFE59223CF548C5661A194AF2B78E7163E50FE58A4348811D91BD9B0010E483" height=24160804 module=consensus round=0
Halted block: https://paloma.explorers.guru/block/24160803
This is where the panic is coming from. Given that it panics all the way down in the store implementation, I don't really understand why they're catching an error here and also try to handle the case of value not found.
But ultimately it means this grant wasn't found when expected to be there. @maharifu You're more involved with the authz module, I imagine we can assume the grant exists at this point, seeing as there's already a TX that contains a dispatch call, and other nodes didn't panic?
If so, this is the third occurrence we've come across of the IAVL implementation not persisting files accordingly in some cases. We've been in touch with the Cosmos team, but they didn't really have an explanation for this either.
We're looking to upgrade to v0.50.9
, which might contain bug fixes to address this issue.
For the specific transaction on that block, the grant should be there:
grants:
- authorization:
type: cosmos-sdk/GenericAuthorization
value:
msg: /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
grantee: paloma1gh3c0mqrrc40057vtydxhy8pk27a5yhffpsh23
granter: paloma182ettr33r6cjh5sly58rl75wzcw8dn65pmey6x
- authorization:
type: cosmos-sdk/GenericAuthorization
value:
msg: /cosmos.staking.v1beta1.MsgDelegate
grantee: paloma1gh3c0mqrrc40057vtydxhy8pk27a5yhffpsh23
granter: paloma182ettr33r6cjh5sly58rl75wzcw8dn65pmey6x
pagination:
total: "2"
I agree this seems related to a previous issue and we should upgrade.
Sorry. Wrong ticket!
What is happening?
Getting wrong Block.Header.AppHash after this
Paloma and pigeon versions and logs
Section description
Write down paloma version. Write down pigeon version. Copy and paste pigeon config file as well as relevant ENV variables.v2.2.1