I get an error function call

[Itoro-Brown]

Please what is wrong with this code I get an error anytime I try to run it.

async function main() {
  const SimpleStorageFactory = await ethers.getContractFactory("kucoin");
  console.log("Deploying the contract....");
  const SimpleStorage = await SimpleStorageFactory.deploy();
  await SimpleStorage.deploy();

  console.log(`Deployed contract to this address:${SimpleStorage.address}`);
}

This is the error I get " Contract. deploy is not a function"
```

[othaime-en]

You've deployed the contract factory twice

const SimpleStorage = await SimpleStorageFactory.deploy();
await SimpleStorage.deploy();

The first deploy is enough and SimpleStorage is already a deployed contract
remove the line await SimpleStorage.deploy() and see if it works

[krakxn]

@othaime-en That is wrong, we need the following to wait till it is deployed; so, just deploy will not be enough.

This should fix it:

const SimpleStorage = await SimpleStorageFactory.deploy();
-await SimpleStorage.deploy();
+await SimpleStorage.deployed();

[othaime-en]

Oh shoot. My bad.

Though technically, as per the ethers documentation once you run contractFactory.deploy() (or in this case SimpleStorageFactory.deploy() ) The contract address is already available to you. Which is the case here seeing as @Itoro-Brown wanted to log where the contract was deployed.

He could add await SimpleStorage.deployTransaction.wait(1) just to make sure the transaction is mined before logging the contract address too.

Your way works too though. Neat approach.

[krakxn]

Yes, that works too -- and a higher amt. of blocks mined for a testnet.

However, I would prefer adopting deployed() instead, as it returns a promise (resolves or rejects) -- which makes it much more flexible and precise.

[othaime-en]

Yeah you right. Since he is using hardhat-ethers here, best practice would be adopting .deployed()