gents, amidst the whirlwind of SEAL 911 tickets, I somehow managed (don’t ask me how!) to add support for off-chain message hashes to my Safe transaction hashes Bash script over the past few days. The updated script now outputs the raw message, along with the domain, message, and Safe message hashes, making it easy for you to verify them against the values shown on your Ledger hardware wallet screen. This can be particularly useful for security councils using 1/1 multisigs to sign into governance tools or for logging into platforms like OpenSea with your multisig. Always remember: Don't trust, verify!
https://github.com/pcaversaccio/safe-tx-hashes-util/pull/10
On a side note, I've been asked a few times over the last weeks how people can support my open-source work. Everything I create is for the community, with the goal of strengthening our ecosystem's security/tooling suite (this includes snekmate, CreateX, xdeployer etc.). If you feel like showing your appreciation, you can find my donation address here https://github.com/pcaversaccio/snekmate/blob/main/FUNDING.json#L4
✨ Add Support for Off-Chain Message Hashes by pcaversaccio · Pull Request #10 · pcaversaccio/safe-tx-hashes-util
🕓 Changelog This PR introduces support for computing the corresponding hashes for off-chain messages following the EIP-712 standard. To calculate the Safe message hashes for a specific message, spe...