Contract Deployment – Fixing “Invalid Transaction Envelope Type: Specified Type” Error in MyEtherWallet

I launched the geth node using a different network id than the chain id configured in genesis.json. By default, web3 will look up the network id from the node and uses it in the transaction, but this would be an invalid transaction as the genesis block states a different chain id.

I had no idea chain id and network id were one and the same. I adjusted the network id on the node to match the configured chain id and there were no issues anymore. Alternatively specifying the correct chainId when signing the transaction will also work.

Yes, tokens are technically created out of thin air. On mainnet it is seen as coming from the zero address.

What you need to do in this case is rather add an input paramater to the constructor for example:

 constructor()ERC20(TOKEN_NAME, TOKEN_SYMBOL, address payable _initialPayWallet) {
    _mint(_initialPayWallet, TOTAL_SUPPLY);
  }

That should work.