# EVM Methods

{% embed url="<https://docs.walletconnect.com/advanced/rpc-reference/ethereum-rpc>" %}

### **eth\_sendTransaction**

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

* Parameters

  ```json
  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
  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.
  ```
* Returns

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

  ```json
  // Request
  {
    "id": 1,
    "jsonrpc": "2.0",
    "method": "eth_sendTransaction",
    "params":[
  	  {
  	    from: "0xb60e8dd61c5d32be8058bb8eb970870f07233155",
  	    to: "0xBDE1EAE59cE082505bB73fedBa56252b1b9C60Ce",
  	    data: "0x",
  	    gasPrice: "0x029104e28c",
  	    gas: "0x5208",
  	    value: "0x00"
  	  }
  	]
  }

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

### **eth\_signTransaction**

: Signs a transaction that can be submitted to the network at a later time using with `eth_sendRawTransaction`

* Parameters

  ```json
  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
  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.
  ```
* Returns

  ```json
  DATA - the signed transaction data
  ```
* Example

  ```json
  // Request
  {
    "id": 1,
    "jsonrpc": "2.0",
    "method": "eth_signTransaction",
    "params":[
  	  {
  	    from: "0xb60e8dd61c5d32be8058bb8eb970870f07233155",
  	    to: "0xd46e8dd67c5d32be8058bb8eb970870f07244567",
  	    data: "0xd46e8dd67c5d32be8d46e8dd67c5d32be8058bb8eb970870f072445675058bb8eb970870f072445675",
  	    gas: "0x76c0", // 30400
  	    gasPrice: "0x9184e72a000", // 10000000000000
  	    value: "0x9184e72a", // 2441406250
  	    nonce: "0x117" // 279
  	  }
  	]
  }

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

### **personal\_sign**

* Parameters

  ```json
  1. DATA, N Bytes - message to sign.
  2. DATA, 20 Bytes - address.
  ```
* Returns

  ```json
  DATA: Signature
  ```
* Example

  ```json
  // Request
  {
    "id": 1,
    "jsonrpc": "2.0",
    "method": "personal_sign",
    "params":["0xdeadbeaf","0x9b2055d370f73ec7d8a03e965129118dc8f5bf83"]
  }

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


---

# 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://docs.neopin.io/developers/walletconnect-2.0/methods/evm-methods.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.