Metamask: Deploy a contract using a second address in the wallet using a helmet

Here is an article on deploying a contract with Hardhat using a secondary address in your Metamask wallet:

Deploying a contract using your secondary address in your MetaMask wallet with Hardhat

When developing smart contracts, it is important to keep track of multiple addresses and the assets associated with them. One common scenario involves multiple wallets, each with different accounts or assets. In this article, we will explore how to deploy a contract using your secondary address in your wallet (Metamask) from a project created with Hardhat.

Understanding the Hardhat Configuration

Before diving into contracts, it is important to understand the configuration file that Hardhat uses in development and production environments. For local development, you can use the following specifications:

module.exports = {
// Your network provider (e.g. infura, ethersgorp)
network: {
provider: '
network_id: 1,
},
// Wallet provider (Metamask)
wallet provider: {
privateKey: '',
mnemonic: '',
gas price: 20 * Math.pow(10, 18),
},
// Your project's starting point
entries: [
{ from: '0xYourAccountAddress', to: '0xContractAddress', args: ['arg1', 'arg2'] },
],
};

In the example above:

• “network”: Provider and network information.

• “walletProvider”: Your MetaMask wallet configuration, including private key, note, and gas price.

• “entries”: A set of contract deployment configurations.

Deploying Contracts with Hardhat

If you want to deploy a contract using a different address from your Metamask wallet with Hardhat, you need to create an environment file (.env or hardhat.config.js) for each wallet. This file will define the private key and other metadata.

Create a new file named .env in the root of your project:

METAMASK_PRIVATE_KEY=my_metascan_private_key

Alternatively, you can use Hardhat’s built-in configuration feature to define an environment file with one entry for each wallet.

module.exports = {
// Your network provider (e.g. infura, ethersgorp)
network: "development",
// MetaMask wallets
envFiles: {
'metamask1': {
privateKey: '',
mnemonic: '',
gas price: 20 * Math.pow(10, 18),
},
'metamask2': {
privateKey: '',
mnemonic: '',
gas price: 20 * Math.pow(10, 18),
},
},
};

Now create a new file called “hardhat.config.js” with the following definitions:

const { ethers } = require('ethers');
const envFiles = require('./envFiles');
module.exports = {
// Your project's starting point
entries: [
{ from: 'metamask1', to: '0xContractAddress_1', args: ['arg1', 'arg2'] },
{ from: 'metamask2', to: '0xContractAddress_2', args: ['arg3', 'arg4'] },
],
};

Deployment Contracts

With the envFiles configuration in place, you can now use Hardhat to deploy contracts. In your main.js file or any other starting point:

“` javascript

const { ethers } = require(‘ethers’);

const { envFiles } = require(‘./hardhat.config’);

async function main() {

// Import the contract ABI and bytecode

const contractAbi = await import(‘./path/to/contract/abi.json’);

const contractBytecode = await import(‘./path/to/contract bytecode.json’);

// Get accounts from environment files

const { metamask1, metamask2 } = envFiles;

// Deploy the contract with Hardhat’s deploy function

const deployer = new ethers.providers.JsonRpcProvider(

“

{

gas price: 20 * Math.pow(10, 18),

}

);

const accounts = await deploy.