> For the complete documentation index, see [llms.txt](https://docs.neopin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neopin.io/developers/deprecated/deprecated-neopin-connect-1.0/json-rpc-api-methods.md).

# JSON-RPC API Methods

{% hint style="danger" %}
The following information is deprecated and may limit its use. Please refer to the WalletConnect 2.0 tab for the latest version of NEOPIN wallet integration: [WalletConnect 2.0](/developers/walletconnect-2.0.md)
{% endhint %}

### eth\_sendTransaction[​](https://docs.walletconnect.com/json-rpc-api-methods/ethereum#eth_sendtransaction) <a href="#eth_sendtransaction" id="eth_sendtransaction"></a>

Creates new message call transaction or a contract creation, if the data field contains code.

#### Parameters[​](https://docs.walletconnect.com/json-rpc-api-methods/ethereum#parameters-3) <a href="#parameters-3" id="parameters-3"></a>

1. Object - The transaction object
2. from: DATA, 20 Bytes - The address the transaction is send from.
3. to: DATA, 20 Bytes - (optional when creating new contract) The address the transaction is directed to.
4. data: DATA - The compiled code of a contract OR the hash of the invoked method signature and encoded parameters. For details see [Ethereum Contract ABI](https://github.com/ethereum/wiki/wiki/Ethereum-Contract-ABI)
5. gas: QUANTITY - (optional, default: 90000) Integer of the gas provided for the transaction execution. It will return unused gas.
6. gasPrice: QUANTITY - (optional, default: To-Be-Determined) Integer of the gasPrice used for each paid gas
7. value: QUANTITY - (optional) Integer of the value sent with this transaction
8. nonce: QUANTITY - (optional) Integer of a nonce. This allows to overwrite your own pending transactions that use the same nonce.

#### Example Parameters[​](https://docs.walletconnect.com/json-rpc-api-methods/ethereum#example-parameters-1) <a href="#example-parameters-1" id="example-parameters-1"></a>

```json
[
    {
        "from": "0xb60e8dd61c5d32be8058bb8eb970870f07233155",
        "to": "0xd46e8dd67c5d32be8058bb8eb970870f07244567",
        "data": "0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675",
        "gas": "0x76c0", // 30400
        "gasPrice": "0x9184e72a000", // 10000000000000
        "value": "0x9184e72a", // 2441406250
        "nonce": "0x117" // 279
    }
]
```

#### Returns[​](https://docs.walletconnect.com/json-rpc-api-methods/ethereum#returns-3) <a href="#returns-3" id="returns-3"></a>

DATA, 32 Bytes - the transaction hash, or the zero hash if the transaction is not yet available.

#### Example[​](https://docs.walletconnect.com/json-rpc-api-methods/ethereum#example-3) <a href="#example-3" id="example-3"></a>

```json
// Request
{
    "id": 1,
    "jsonrpc": "2.0",
    "method": "eth_sendTransaction",
    "params":[{see above}],
}

// Result
{
    "id": 1,
    "jsonrpc": "2.0",
    "result": "0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331"
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.neopin.io/developers/deprecated/deprecated-neopin-connect-1.0/json-rpc-api-methods.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.