β¨ Add Support for Berachain, Ink, Sonic, and Unichain #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Changelog
This PR (supersedes #28) adds support for the following additional chains:
berachain, chain ID:80094),ink, chain ID:57073),sonic, chain ID:146),unichain, chain ID:130).All supported chains that use the Safe transaction service API can be retrieved via:
curl -s https://safe-config.safe.global/api/v1/chains/ | jq '.results[].chainName'Test Example:
./safe_hashes.sh --network sonic --address 0x9deDd0B4BDb5c55fB067C990a9D45BDEc465615e --nonce 3returns:
Now compare with https://app.safe.global/transactions/tx?safe=sonic:0x9deDd0B4BDb5c55fB067C990a9D45BDEc465615e&id=multisig_0x9deDd0B4BDb5c55fB067C990a9D45BDEc465615e_0x94aa3ee3649f35d14838e1b731fc6b4fb9c7ec9c5dd9028c4368b9964d76b6ae.