deploy: mainnet: InventoryStaking, NFTXVault implementation

Author: apoorvlathey

README.md

@@ -151,14 +151,14 @@ forge test
 1. To deploy core V3 contracts (including Uniswap V3 Fork):
 
 ```sh
-yarn deploy:goerli --maxfee <inWei> --priorityfee <inWei> --tags NFTXV3
+yarn deploy:mainnet --maxfee <inWei> --priorityfee <inWei> --tags NFTXV3
 ```
 
 2. Deploy new Universal Router (https://github.com/NFTX-project/nftx-universal-router) with updated address for UniswapV3 Factory address.
 3. Deploy all Zaps:
 
 ```sh
-yarn deploy:goerli --maxfee <inWei> --priorityfee <inWei> --tags Zaps
+yarn deploy:mainnet --maxfee <inWei> --priorityfee <inWei> --tags Zaps
 ```
 
 4. Run the following to generate `./addresses.json` for the deployed contract addresses
@@ -171,11 +171,11 @@ Note: Tags are defined in the deploy script at the end like: `func.tags = ["<tag
 
 ### Verify Contracts
 
-`yarn verify:goerli`
+`yarn verify:mainnet`
 
 **Note:** For some UniswapV3 contracts there might be some error while verifying, so run this for those contracts:
 
-`yarn verify:goerli --license "GPL-2.0" --force-license --solc-input`
+`yarn verify:mainnet --license "GPL-2.0" --force-license --solc-input`
 
 - How to verify the Create2BeaconProxy (for Vaults):
 

deployments/mainnet/NFTXInventoryStakingV3Upgradeable.json

@@ -1147,7 +1147,7 @@
       "0x39D9A925d7fcA17E430b731882b97e2d10E9F8bB"
     ]
   },
-  "implementation": "0x8E912C466bD1D720b7d97034c03572c4A261de33",
+  "implementation": "0xF76e6B0029cb2D6D41B321E5BEb2e849d345081A",
   "devdoc": {
     "details": "This contract implements a proxy that is upgradeable by an admin. To avoid https://medium.com/nomic-labs-blog/malicious-backdoors-in-ethereum-proxies-62629adf3357[proxy selector clashing], which can potentially be used in an attack, this contract uses the https://blog.openzeppelin.com/the-transparent-proxy-pattern/[transparent proxy pattern]. This pattern implies two things that go hand in hand: 1. If any account other than the admin calls the proxy, the call will be forwarded to the implementation, even if that call matches one of the admin functions exposed by the proxy itself. 2. If the admin calls the proxy, it can access the admin functions, but its calls will never be forwarded to the implementation. If the admin tries to call a function on the implementation it will fail with an error that says \"admin cannot fallback to proxy target\". These properties mean that the admin account can only be used for admin actions like upgrading the proxy or changing the admin, so it's best if it's a dedicated account that is not used for anything else. This will avoid headaches due to sudden errors when trying to call a function from the proxy implementation. Our recommendation is for the dedicated account to be an instance of the {ProxyAdmin} contract. If set up this way, you should think of the `ProxyAdmin` instance as the real administrative interface of your proxy.",
     "kind": "dev",

deployments/mainnet/NFTXInventoryStakingV3Upgradeable_Implementation.json

@@ -132,14 +132,14 @@ forge test
 1. To deploy core V3 contracts (including Uniswap V3 Fork):
 
 ```sh
-yarn deploy:goerli --maxfee <inWei> --priorityfee <inWei> --tags NFTXV3
+yarn deploy:mainnet --maxfee <inWei> --priorityfee <inWei> --tags NFTXV3
 ```
 
 2. Deploy new Universal Router (https://github.com/NFTX-project/nftx-universal-router) with updated address for UniswapV3 Factory address.
 3. Deploy all Zaps:
 
 ```sh
-yarn deploy:goerli --maxfee <inWei> --priorityfee <inWei> --tags Zaps
+yarn deploy:mainnet --maxfee <inWei> --priorityfee <inWei> --tags Zaps
 ```
 
 4. Run the following to generate `./addresses.json` for the deployed contract addresses
@@ -152,11 +152,11 @@ Note: Tags are defined in the deploy script at the end like: `func.tags = ["<tag
 
 ### Verify Contracts
 
-`yarn verify:goerli`
+`yarn verify:mainnet`
 
 **Note:** For some UniswapV3 contracts there might be some error while verifying, so run this for those contracts:
 
-`yarn verify:goerli --license "GPL-2.0" --force-license --solc-input`
+`yarn verify:mainnet --license "GPL-2.0" --force-license --solc-input`
 
 - How to verify the Create2BeaconProxy (for Vaults):