Automatically check the domain and message hashes sent to Ledger matches the ones in the simulation
#195 ouverte le 10 mai 2024
Métriques du dépôt
- Stars
- (98 étoiles)
- Métriques de merge PR
- (Merge moyen 2j 4h) (16 PRs mergées en 30 j)
Description
Recently, due to a bug fixed in https://github.com/base-org/contract-deployments/pull/166/files, we were getting different hashes sent to the ledger devices compared to the ones in the Tenderly simulation. It would be great if we can detect this by automatically checking the domain and message hashes sent to Ledger matches the ones in the simulation. This may require us to migrate away from Tenderly to a more programmatically parsable one.
See https://www.notion.so/oplabs/PM-48-Wrong-message-hash-sent-to-Signers-Ledger-during-an-L2-contract-upgrade-c893131d9daa440bad6fe09c848db54d for the original postmortem