You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -42,6 +43,7 @@ This is a series of steps to deploy the token to production and upgrade it if ne
42
43
### Safe wallet creation
43
44
44
45
First we create a wallet in [Safe](https://app.safe.global/) to represent the foundation. We assume this is done by the user. This safe will:
46
+
45
47
- Receive part of the deployed tokens.
46
48
- Own the proxy admin contract. This is the contract that can upgrade the token contract.
47
49
- Own the proxy contract. This will point to the current implementation of the contract. All users and the safe itself will interact with this contract to mint, transfer, burn, and other erc20 operations.
@@ -51,7 +53,7 @@ First we create a wallet in [Safe](https://app.safe.global/) to represent the fo
51
53
There is an example configuration file in `script-config/config.example.json`. Before deploying to production, we need to create a `config.mainnet.json` file in the same folder with the same contents as the example, but we need to change a couple of fields:
52
54
53
55
-`foundation`: this is the address of the safe that was created in the previous step.
54
-
-`claimSupplier`: this is the address of a different safe that will provide the funds for the claim contract when it is deployed.
56
+
-`tokenDistributor`: this is the address of a different safe that will provide the funds for the claim contract when it is deployed.
55
57
-`deployer`: The address of the deterministic create2 deployer as specified in the [official repo](https://github.com/Arachnid/deterministic-deployment-proxy). The address should be `0x4e59b44847b379578588920ca78fbf26c0b4956c`.
56
58
-`salt`: An arbitrary value provided by the sender. This is a 32-bytes hex string. We default to 0.
57
59
@@ -69,6 +71,7 @@ This make target internally executes a forge script that:
69
71
The private key does NOT correspond to the safe, it needs to represent an account with sufficient funds to deploy the token.
70
72
71
73
Arguments (env variables):
74
+
72
75
-`PRIVATE_KEY`: the private key of the deployer account. This is NOT the foundation safe, just any account with enough eth for the deployment. This operation consumes approximately `3935470` gas units. As of Dec 16 2024, the gas price for a high priority is 16 gwei, which means around `0.063` eth.
73
76
-`RPC_URL`: a gateway or node that allows for rpc calls.
74
77
-`CONFIG`: the name of the configuration file. For `config.example.json` the name would be `example`. For `config.mainnet.json`, this would be `mainnet`.
0 commit comments