deployed FT dev

.env.example

@@ -31,9 +31,13 @@ FT_CONFIGURATOR=
 FINAL_OWNER=
 # Gnosis Safe Address and API key (Optional - Override default safe address for deployments, used with --safe when wiring)
 PRIVATE_KEY_PROPOSER=
+SAFE_API_KEY=
+
+# Here we need to pick one or the other, right?
+# If I use a delegate I don't need an owner, and if I use an owner I don't need a delegate.
 SAFE_DELEGATE_ADDRESS=
 SAFE_OWNER_ADDRESS=
-SAFE_API_KEY=
+
 
 # For verification of contracts on Etherscan, BscScan, SonicScan etc
 ETHERSCAN_API_KEY=

DEPLOYMENT_CHECKLIST.md

@@ -11,6 +11,7 @@ Quick reference checklist for deploying FT token to production.
 - [ ] Set `ETHERSCAN_API_KEY=<key>`
 - [ ] Set `FT_CONFIGURATOR=<multisig-address>` role to have control of initial mint if network is sonic
 - [ ] Set `FINAL_OWNER=<multisig-address>`
+- [ ] Run `pnpm install`
 - [ ] Run `pnpm compile`
 - [ ] Run `pnpm test`
 

deploy/FT.ts

@@ -51,6 +51,7 @@ const deploy: DeployFunction = async (hre) => {
     console.log(`Chain Config: ${chainConfig.name}`);
     console.log(`Configurator: ${ftConfigurator} owner of the initial mint if network is sonic`);
     console.log(`Endpoint V2: ${endpointV2Address}`);
+    // This confused me with safe delegate for the wiring. I guess there is a separate log in the wiring process.
     console.log(`Delegate: ${delegate}`);
     console.log(`Final Owner: ${finalOwner}`);