[New chain]: Hemi Mainnet

[rokso]

Chain Name

Hemi Mainnet

RPC URL

https://8deb9c0b.rpc.hemi.network/rpc

The chain must be added to https://chainlist.org/

• I confirm that the chain is added to chainlist

After creating the issue, a bot will estimate the required pre-fund and post it in the comments. Please check this checkbox after you send the pre-fund.

• I sent the pre-fund in accordance with Github Action's comment

Relevant information

No response

[github-actions]

⛔️ Error:
The factory is already deployed. Please use the existing factory at 0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7.

[rokso]

@nlordell Above factory is deployed as predeploy. How can we add artifact for this factory?

[mmv08]

@rokso you can follow the worldchain example #705 and create a PR yourself

[rokso]

@mmv08 We have 1.4.1 and 1.3.0 canonical deployment on Hemi but there is need for safe 1.3.0 with EIP-155, how can we get factory deployed for this specific version?

[mmv08]

@mmv08 We have 1.4.1 and 1.3.0 canonical deployment on Hemi but there is need for safe 1.3.0 with EIP-155, how can we get factory deployed for this specific version?

the same factory is used for 1.4.1 and 1.3.0 with eip-155, it's a general purpose create2 factory :)

[rokso]

@mmv08 We have 1.4.1 and 1.3.0 canonical deployment on Hemi but there is need for safe 1.3.0 with EIP-155, how can we get factory deployed for this specific version?

the same factory is used for 1.4.1 and 1.3.0 with eip-155, it's a general purpose create2 factory :)

So how we go about deploying factory at 0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC. We need this factory to claim same safe address as on OP/Base.

[mmv08]

@mmv08 We have 1.4.1 and 1.3.0 canonical deployment on Hemi but there is need for safe 1.3.0 with EIP-155, how can we get factory deployed for this specific version?

the same factory is used for 1.4.1 and 1.3.0 with eip-155, it's a general purpose create2 factory :)

So how we go about deploying factory at 0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC. We need this factory to claim same safe address as on OP/Base.

See this paragraph in the docs here: https://github.com/safe-global/safe-smart-account/tree/v1.3.0-libs.0?tab=readme-ov-file#replay-protection-eip-155

You'll most likely need to replace the @gnosis.pm/safe-singleton-factory package with @safe-global/safe-singleton-factory or add the deployment artifact manually to the node_modules folder or edit the hardhat config directly

[rokso]

@mmv08 I was able to use this factory to deploy 1.3.0-libs-0 contracts. Thanks for pointing me in the right direction.