RPC method

eth_sendRawTransaction on Abstract

Supported on SwiftNodes

Everything below was measured on 2026-10-13 by calling eth_sendRawTransaction on Abstract through the same endpoint customers use, and is re-measured weekly.

What eth_sendRawTransaction does

Submits a signed transaction to the network and returns its hash. The node checks the signature, chain ID, nonce and balance first, and returns an error string instead of a hash when any check fails, which is the text your app has to handle.

Errors Abstract returns, word for word

We submitted three transactions that must fail, signed by a new, empty key (nothing was spent). These are the messages your app receives in those situations.

EIP-1559 transfer from an empty account	insufficient funds for gas + value. balance: 0, fee: 1900500021000, value: 1
Legacy transaction signed without a chain ID (pre-EIP-155)	insufficient funds for gas + value. balance: 0, fee: 1900500021000, value: 1
Truncated bytes ("0x02f8")	Failed to serialize transaction: decodeRlpError RlpIsTooShort

How to read them

"insufficient funds" means the balance cannot cover value + gas limit × max fee per gas.

Abstract's nodes did not refuse the unprotected transaction for lacking a chain ID; it reached the balance check. Such a transaction could be replayed on any chain where the account has funds, so always sign with the chain ID (2741).

Send the same signed bytes again only if you never got a hash back: a second submission of an accepted transaction returns an "already known" style error, not a second transaction, and a transaction with the same nonce but a higher fee replaces it.

Example request

curl -s https://rpc.swiftnodes.io/rpc/abstract?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_sendRawTransaction","params":["0x02f8..."]}'

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/abstract?key=YOUR_API_KEY"),
});

try {
  const hash = await client.sendRawTransaction({ serializedTransaction: signed });
  const receipt = await client.waitForTransactionReceipt({ hash });
} catch (e) {
  const msg = String(e?.details ?? e?.message);
  if (/insufficient funds/i.test(msg)) { /* ask the user to top up */ }
  else if (/nonce too low|already known/i.test(msg)) { /* already sent: look up by hash */ }
  else throw e;
}

Other methods on Abstract

eth_blockNumberSupported
eth_chainIdSupported
eth_getBalanceSupported
eth_getBlockByNumberSupported
eth_getTransactionByHashSupported
eth_getTransactionReceiptSupported
eth_callSupported
eth_estimateGasNot measured
eth_gasPriceSupported
eth_maxPriorityFeePerGasSupported
eth_getTransactionCountSupported
eth_getCodeSupported
eth_subscribeSupported
eth_getLogsSupported
eth_getBlockReceiptsSupported
eth_feeHistorySupported
eth_getProofNot available
eth_createAccessListNot available
debug_traceCallSupported
trace_blockNot available
trace_transactionNot available

eth_sendRawTransaction on other chains

Frequently asked questions

Does Abstract support eth_sendRawTransaction?

Yes. eth_sendRawTransaction answered on the SwiftNodes Abstract endpoint when our weekly probe called it through the customer path (2026-10-13).

Does Abstract accept transactions without a chain ID?

Its nodes did not refuse one for that reason in our test (2026-10-13); sign with chain ID 2741 anyway.

Why does Abstract return "insufficient funds" from eth_sendRawTransaction?

The sender cannot pay value plus gas limit × maxFeePerGas. Fund the account, lower the value, or lower maxFeePerGas.

Abstract endpoints, live block height and WebSocket status are on the Abstract RPC page.

One key covers every chain we serve, and SwiftNodes has a free tier.