Adding a placeholder for Pinata JWT in .env.example

aragon · Feb 12, 2025 · 2fe5572 · 2fe5572
1 parent cccd6af
commit 2fe5572
Showing 1 changed file with 6 additions and 3 deletions.
diff --git a/packages/contracts/.env.example b/packages/contracts/.env.example
@@ -3,6 +3,12 @@ ETHERSCAN_KEY=<Etherscan-Api-Key>
 POLYGONSCAN_KEY=<Polygonscan-Api-Key>
 ARBISCAN_KEY=<Arbiscan-Api-Key>
 
+## To deploy contracts, you need to set:
+PUB_PINATA_JWT=""
+
+## Alchemy RPC endpoint credentials
+ALCHEMY_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
+
 COINMARKETCAP_API_KEY=<Coinmarketcap-Api-Key>
 
 MAINNET_DAO_ENS_DOMAIN=<ENS-Domain example: dao.eth>
@@ -50,6 +56,3 @@ HARDHAT_MANAGEMENT_DAO_MULTISIG=0xe3ADd897e69010709498738e5116C06B4D81e672 # Cha
 
 # not using this variable will disable the feature. Anything else will enable it
 TEST_UPDATE_DEPLOY_SCRIPT=
-
-## Alchemy RPC endpoint credentials
-ALCHEMY_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"