#Different actions hash result between on-chain and archive node when fetching actions in Lightnet

3 messages · Page 1 of 1 (latest)

gritty radish
#

Has anyone came across this error?

Error: Failed to derive correct actions hash for B62qovNcjV7L6BQEZu8tHBocUZetcnuzKWLyjp2ZEMpkQeHMSUF5MWL.
        Derived hash: 5288754271501479736494962873291837598958669628103147322012038566724573103926, expected hash: 8009927662518731636002744210010355288003620018262091383684232283845324346968).
        All action hashes derived: [...] 
```

Environment:
- o1js: 0.18.0
- zkapp-cli: 0.19.0

I have this error while fetching actions of smart contracts deployed on Lightnet with `Mina.fetchActions(...)`. From the list of the actions return by archive node, what's happening is one of the action generated different actionState value from the on-chain value (graphql), which breaking the hash chain and derive incorrect final actionState value.

It occurs unexpectedly and hard to reproduce, I suspect the reason is from the lightnet network because it also occurs to zkApps not having any new actions (previously fetching actions correctly).
#

Different actions hash result between on-chain and archive node when fetching actions in Lightnet

native lion