> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.
# eth_sendRawTransaction | Hyperliquid EVM
> The eth_sendRawTransaction JSON-RPC method submits a pre-signed transaction to the network for broadcasting and inclusion in a block.
This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
The `eth_sendRawTransaction` JSON-RPC method submits a pre-signed transaction to the network for broadcasting and inclusion in a block. This method is essential for sending transactions that have been signed offline or by external wallets, enabling secure transaction submission without exposing private keys.
**Get your own node endpoint today**
[Start for free](https://console.chainstack.com/) 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
The method takes one parameter:
1. **Signed transaction data** — The signed raw transaction data
### Parameter details
* `signedTransactionData` (string, required) — The signed transaction data in hexadecimal format with `0x` prefix
## Response
The method returns the transaction hash if the transaction was successfully submitted to the network.
### Response structure
**Transaction hash:**
* `result` — The 32-byte transaction hash as a hexadecimal string
### Transaction status
**Submission outcomes:**
* Success returns a transaction hash immediately
* The hash does not guarantee inclusion in a block
* Use `eth_getTransactionReceipt` to confirm inclusion
* Failed transactions may still consume gas
**Common errors:**
* `nonce too low` — Transaction nonce already used
* `insufficient funds` — Account lacks funds for gas + value
* `gas limit exceeded` — Transaction gas limit too high
* `transaction underpriced` — Gas price below network minimum
## Hyperliquid-specific considerations
### Transaction requirements
**Gas and fees:**
* Transactions require HYPE for gas fees
* Gas prices fluctuate based on network demand
* Use `eth_gasPrice` to get current gas price
* Consider priority fees for faster inclusion
### Transaction monitoring
**Confirmation tracking:**
* Monitor transaction status with `eth_getTransactionReceipt`
* Check for transaction replacement by monitoring nonce
* Verify block confirmations for finality
* Handle reorg scenarios appropriately
## Example request
```shell Shell theme={"system"}
curl -X POST https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "eth_sendRawTransaction",
"params": [
"f86d80843b9aca0082520894b7c609cffa0e47db2467ea03ff3e598bf59361a5880de0b6b3a7640000808207f2a02d013b9980176ca8674f77797ac04e928b8de3be92dd452501ec26acbb2b1abca054041f43109eeadbb4d6b712a20dc71e5dbe1225e549644be3de803b55041a89"
],
"id": 1
}'
```
## Use cases
The `eth_sendRawTransaction` method is essential for applications that need to:
* **Wallet applications**: Submit user-signed transactions to the network
* **DeFi protocols**: Execute pre-signed transactions for swaps and liquidity operations
* **Trading bots**: Submit high-frequency trading transactions
* **Bridge operations**: Process cross-chain transfer transactions
* **Smart contract interactions**: Deploy contracts and execute contract methods
* **Batch operations**: Submit multiple pre-signed transactions sequentially
* **Multisig wallets**: Submit transactions signed by multiple parties
* **Hardware wallets**: Broadcast transactions signed offline
* **Payment systems**: Process payment transactions securely
* **Token transfers**: Send ERC-20, ERC-721, and ERC-1155 token transfers
* **Staking operations**: Submit staking and delegation transactions
* **Governance voting**: Cast votes in on-chain governance systems
* **NFT minting**: Submit minting transactions for NFT collections
* **Liquidation bots**: Execute time-sensitive liquidation transactions
* **Arbitrage systems**: Submit profitable arbitrage transactions quickly
* **Meta-transactions**: Process gasless transactions via relayers
* **Scheduled transactions**: Submit pre-signed future transactions
* **Recovery operations**: Broadcast recovery transactions for compromised accounts
* **Testing frameworks**: Submit test transactions in development environments
* **Analytics tools**: Monitor transaction submission patterns
* **Security systems**: Submit security-related transactions like pausing contracts
* **Compliance tools**: Process regulatory-required transactions
* **Integration services**: Bridge web2 and web3 transaction systems
* **Mobile applications**: Submit transactions from mobile wallets
* **Game transactions**: Process in-game asset transfers and purchases
This method provides the fundamental capability to submit transactions to the Hyperliquid EVM network, enabling all transaction-based operations on the platform.
Ensure your transaction is properly signed and includes the correct nonce, gas price, and gas limit before submission. Failed transactions will still consume gas fees. Always verify the transaction hash returned and monitor its status using `eth_getTransactionReceipt`.
## OpenAPI
````yaml /openapi/hyperliquid_node_api/evm_eth_send_raw_transaction.json post /evm
openapi: 3.0.0
info:
title: Hyperliquid EVM API - eth_sendRawTransaction
version: 1.0.0
servers:
- url: >-
https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274
security: []
paths:
/evm:
post:
summary: eth_sendRawTransaction
description: >-
Submits a pre-signed transaction to the network for broadcasting and
inclusion in a block.
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- jsonrpc
- method
- params
- id
properties:
jsonrpc:
type: string
enum:
- '2.0'
default: '2.0'
description: JSON-RPC version
method:
type: string
enum:
- eth_sendRawTransaction
default: eth_sendRawTransaction
description: The RPC method name
params:
type: array
description: 'Parameters: [signedTransactionData]'
default:
- >-
f86d80843b9aca0082520894b7c609cffa0e47db2467ea03ff3e598bf59361a5880de0b6b3a7640000808207f2a02d013b9980176ca8674f77797ac04e928b8de3be92dd452501ec26acbb2b1abca054041f43109eeadbb4d6b712a20dc71e5dbe1225e549644be3de803b55041a89
id:
type: integer
default: 1
description: Request identifier
example:
jsonrpc: '2.0'
method: eth_sendRawTransaction
params:
- >-
f86d80843b9aca0082520894b7c609cffa0e47db2467ea03ff3e598bf59361a5880de0b6b3a7640000808207f2a02d013b9980176ca8674f77797ac04e928b8de3be92dd452501ec26acbb2b1abca054041f43109eeadbb4d6b712a20dc71e5dbe1225e549644be3de803b55041a89
id: 1
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
properties:
jsonrpc:
type: string
example: '2.0'
id:
type: integer
example: 1
result:
type: string
description: The transaction hash
example: >-
0xe670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331
'400':
description: Bad request
content:
application/json:
schema:
type: object
properties:
jsonrpc:
type: string
example: '2.0'
id:
type: integer
example: 1
error:
type: object
properties:
code:
type: integer
example: -32000
message:
type: string
example: nonce too low
````