POST
/
4ab982aa70a7baead515ffdb5915df3f
curl --request POST \
  --url https://fantom-mainnet.core.chainstack.com/4ab982aa70a7baead515ffdb5915df3f \
  --header 'Content-Type: application/json' \
  --data '{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "eth_getCode",
  "params": [
    "0x21be370D5312f44cB42ce377BC9b8a0cEF1A4C83",
    "latest"
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": {}
}

Fantom API method that retrieves the compiled bytecode of a smart contract, providing its address as a parameter. This method returns a hexadecimal string representing the smart contract’s bytecode.

Developers can use this bytecode to verify whether a smart contract is legitimate and ensure that it performs its intended functions.

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • address — the address of the smart contract to query.

  • quantity or tag — the integer of a block encoded as hexadecimal or the string with:

    • latest — the most recent block in the blockchain and the current state of the blockchain at the most recent block. A chain reorganization is to be expected.
    • safe — the block that received justification from the beacon chain. Although this block could be involved in a chain reorganization, it would necessitate either a coordinated attack by the majority of validators or an instance of severe propagation latency.
    • finalized — the block accepted as canonical by more than 2/3 of the validators. A chain reorganization is extremely unlikely, and it would require at least 1/3 of the staked amount to be burned.
    • earliest — the earliest available or genesis block.
    • pending — the pending state and transactions block. The current state of transactions that have been broadcast to the network but have not yet been included in a block.

See the default block parameter and How The Merge Impacts Ethereum’s Application Layer.

​
Response

data — the compiled bytecode of a smart contract. Returns 0x if the address is not associated with a smart contract.

​
eth_getCode code examples

The following example retrieves the compiled bytecode from the WFTM token smart contract.

const { Web3 } = require("web3");
const NODE_URL = "CHAINSTACK_NODE_URL";
const web3 = new Web3(NODE_URL);

async function getCode(address, block) {
  const code = await web3.eth.getCode(address, block)
  console.log(code)
 }
 
 getCode("0x21be370D5312f44cB42ce377BC9b8a0cEF1A4C83", "latest" )

​
Use case

A practical use case for the eth_getcode method is verifying whether an address is associated with a smart contract. This can be particularly useful for blockchain explorers, auditors, and DApp developers, who must ensure that the account they interact with is legitimate.

Body

application/json

Response

200 - application/json

The smart contract code.

The response is of type object.