Skip to content

Commit

Permalink
fix: show full address for the deployer
Browse files Browse the repository at this point in the history
  • Loading branch information
Tanay Pant committed Nov 6, 2024
1 parent b4bb9a5 commit 251a8ab
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions pages/core-api/safe-contracts-deployment.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Open a [pull request](https://github.com/ethereum-lists/chains) to add your chai
</Callout>

1. Create a new issue in the [safe-singleton-factory](https://github.com/safe-global/safe-singleton-factory/issues/new?assignees=&labels=&projects=&template=new_chain.yml&title=%5BNew+chain%5D%3A+) repository.
2. A bot will reply to the issue with the deployer address (`0x914...3d7`) and the amount of native token you need to send to this address.
2. A bot will reply to the issue with the deployer address (`0xE1CB04A0fA36DdD16a06ea828007E35e1a3cBC37`) and the amount of native token you need to send to this address.
3. Once funded, mark the checkbox on the GitHub issue.
4. The review of the issues happens every two weeks. Our team will perform the deterministic deployment of the `safe-singleton-factory` contract and publish a new npm release of [@safe-global/safe-singleton-factory](https://www.npmjs.com/package/@safe-global/safe-singleton-factory).

Expand Down Expand Up @@ -105,4 +105,4 @@ For example, add this line to `gnosis_safe.json` to indicate the gnosis safe has

Now, you have deployed the Safe\{Core\} contracts on your chain.

In the next step, you have to install the [Safe\{Core\} Infrastructure](./safe-infrastructure-deployment.mdx).
In the next step, you have to install the [Safe\{Core\} Infrastructure](./safe-infrastructure-deployment.mdx).

0 comments on commit 251a8ab

Please sign in to comment.