Search

Ethereum: Error message “TypeError: Unsupported addressable value (argument=”target”, value=null, code=INVALID_ARGUMENT, version=6.11.1)” when running locally

Ethereum: Error Message Explained – “TypeError: Unsupported addressable value (argument=”target”, value=null, code=INVALID_ARGUMENT, version=6.11.1)”

As a developer who recently deployed your Ethereum-based smart contracts locally using Hardhat, you may have come across an error message that seems scary and confusing. In this article, we will break down the error message “TypeError: Unsupported addressable value (argument=”target”, value=null, code=INVALID_ARGUMENT, version=6.11.1)” to help you understand what it means and how to resolve the issue.

What does the error message mean?

The error message is a technical description of the issue that is occurring on your machine. Here is a breakdown:

  • TypeError: This is a type of error that occurs when a function expects an argument but receives one.
  • unsupported addressable value (argument="target", value=null): This suggests that the getWeth.js script is trying to use an Ethereum wallet as an “address” to send Ether, but is not doing so correctly. The null value represents a missing or invalid argument.
  • (code=INVALID_ARGUMENT, version=6.11.1): This additional information provides more details about the issue:

+ INVALID_ARGUMENT: This error occurs when a function expects an argument that is not valid for its intended purpose.

+ version=6.11.1: This specifies the version of the Ethereum Solidity compiler being used to compile the contract code.

Why is this error occurring?

There are several potential reasons why you are encountering this error:

  • Missing or incorrect wallet address: You may have created a script that expects an Ethereum wallet address, but it is not configured or installed correctly.
  • Invalid or missing getNamedAccounts function call

    : The getNamedAccounts function is used to retrieve the accounts associated with your Ethereum wallet. If this function is not called correctly, or if you are trying to access a non-existent account, you may encounter errors like this.

  • Incorrect contract deployment

    : Make sure your smart contracts are deployed correctly and have the correct addressable values.

How ​​to resolve the issue

To fix the error message, follow these steps:

  • Check the wallet address: Make sure you are using a valid Ethereum wallet address in your script. Check that the address is spelled correctly and matches the one associated with your wallet.
  • Verify getNamedAccounts function call: Verify that the getNamedAccounts function was called correctly and that the correct accounts are being retrieved. Make sure that you are passing the required arguments (e.g. address, from) to this function.
  • Verify contract deployment: Make sure that your smart contracts are deployed correctly with the required addressable values. Check for errors or inconsistencies in the code.

Example fix

Here is an example of how you can modify your script to resolve the issue:

const { getNamedAccounts, ethers } = require("hardhat");

const accounts = await getNamedAccounts({ from: "your-wallet-address" });

const contractAddress = accounts[0].contract;

// Verify that the contract was deployed correctly with the correct addressable values

console.log(Contract Address: ${contractAddress});

By following these steps and examples, you should be able to resolve the error message and successfully deploy your Ethereum-based smart contracts locally using Hardhat.

Smart Smart User Trust

Tinggalkan Komentar

Alamat email Anda tidak akan dipublikasikan. Ruas yang wajib ditandai *

Scroll to Top