# eth\_getCode

### Parameters

* `address`: \[Required] A string representing the address (20 bytes) of the smart contract, from which the compiled byte code will be obtained.
* `block number`: \[Required] A hexadecimal block number, or one of the string tags latest, earliest, pending, safe, or finalized. See the [default block parameter](https://ethereum.org/en/developers/docs/apis/json-rpc/#default-block).

***

### Returns

The compiled byte code of the smart contract at the given address.

> **Note**: If the smart contract has no compiled byte code, the result will be an empty string. And 1Money Network does not support smart contracts, so this method will always return an empty string.

***

### Example

#### Request

```sh
curl -X POST https://testnet.1money.network \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "method": "eth_getCode", "params": ["0x06012c8cf97bead5deae237070f9587f8e7a266d", "0x65a8db"], "id": 1}'
```

#### Response

```sh
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x"
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.1moneynetwork.com/integrations/evm-compatible-rpcs-wip/eth_getcode.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.