Taiko

Taiko

eth_sendRawTransaction

eth_sendRawTransaction submits a fully-signed transaction to the network. It's the only way to produce a state change through a stateless RPC endpoint — every wallet, every contract deployment, every token transfer goes through this method.

The one-line summary

You sign the transaction off-the-wire with the sender's private key, RLP-encode it, prefix with 0x, and hand it to eth_sendRawTransaction. The provider doesn't see the key — only the signed payload.

Parameter

Building a signed transaction

You don't sign by hand. Use a library:

1import { Wallet, JsonRpcProvider } from 'ethers';
2 
3const provider = new JsonRpcProvider('https://ethereum.therpc.io/<YOUR_KEY>');
4const wallet = new Wallet(process.env.PRIVATE_KEY!, provider);
5 
6const tx = await wallet.populateTransaction({
7  to: '0x...',
8  value: 1n * 10n ** 18n,
9});
10const signed = await wallet.signTransaction(tx);
11const hash = await provider.send('eth_sendRawTransaction', [signed]);

For EIP-1559 transactions, set maxFeePerGas and maxPriorityFeePerGas instead of legacy gasPrice. Most modern wallets do this by default.

Response shape

The result is the transaction hash:

1{
2  "jsonrpc": "2.0",
3  "id": 1,
4  "result": "0x9b07f3e8...c4e1"
5}

The hash is final the instant the call returns — but the transaction is not yet on-chain. It's in the mempool. To wait for inclusion, poll eth_getTransactionReceipt with the returned hash, or subscribe via eth_subscribe.

Common failure modes

1. nonce too low / nonce too high — the nonce in the signed payload doesn't match the sender's current nonce. Fetch it fresh via eth_getTransactionCount and rebuild.
2. insufficient funds for gas * price + value — the sender doesn't have enough native-token balance for gas × maxFeePerGas + value.
3. replacement transaction underpriced — you tried to replace a pending tx (same nonce) but with a fee that's not high enough above the original. Most providers require ≥10% bump on both maxFeePerGas and maxPriorityFeePerGas.
4. execution reverted — the EVM rejected the call. The revert reason is decoded by your library; if you got it from a raw RPC response, parse error.data with the contract ABI.

After submission

The tx hash lets you track the lifecycle:

1. Pending — visible via eth_getTransactionByHash, no receipt yet.
2. Mined — eth_getTransactionReceipt returns a receipt with status: "0x1" (success) or "0x0" (revert with gas consumed).
3. Finalised — receipt's blockNumber is now ≤ the chain's finalized tag. Reorg-safe from this point.

See also

• eth_getTransactionReceipt — wait for inclusion + check status.
• eth_estimateGas — get a gas limit before signing.
• eth_call — simulate the call read-only before paying gas.

1curl https://taiko.therpc.io \
2  -X POST \
3  -H 'Content-Type: application/json' \
4  -d '{"jsonrpc":"2.0","id":1,"method":"eth_sendRawTransaction","params":[""]}'