For the complete documentation index, see llms.txt. This page is also available as Markdown.

eth_sendRawTransaction - Tempo

Example code for the eth_sendRawTransaction JSON-RPC method. Complete guide on how to use eth_sendRawTransaction JSON-RPC in GetBlock Web3 documentation.

Broadcasts a signed transaction. Accepts both standard EVM transaction types (0x0 legacy, 0x1 EIP-2930, 0x2 EIP-1559, 0x7702 EIP-7702) and Tempo Transactions (type 0x54) — a Tempo-specific transaction type used for payment flows with structured memo fields, fee-payer sponsorship, and direct routing to subblock proposers. Transactions targeting a specific subblock proposer are routed to the consensus layer when submitted to the matching validator node; other nodes reject them. The transaction value field is effectively ignored — fees and transfers are TIP-20-denominated, not native-token-denominated.

Parameters

Parameter
Type
Required
Description

signedTxData

string

Yes

The signed transaction data (hex). Standard EVM types or Tempo Transaction type 0x54

Request Example

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "eth_sendRawTransaction",
    "params": [
        "0x02f86c8210798504a817c80082520894d85498dbeaeb1df24be52eed4f52eac2fbd56245880de0b6b3a76400008025a04f3a1c..."
    ],
    "id": "getblock.io"
}'

Response Example

Response Parameters

Field
Type
Description

result

string

Transaction hash, used to track inclusion via eth_getTransactionReceipt

Use Cases

  • Submitting TIP-20 stablecoin transfers (the primary Tempo use case)

  • Executing payment flows with attached memos

  • Submitting Tempo Transactions (type 0x54) for advanced payment features

  • Deploying smart contracts on Tempo

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

-32602

Invalid params

Request parameters are missing or malformed

429

Too Many Requests

Rate limit exceeded for your plan

-32000

Insufficient fee token balance

Sender (or fee payer) does not have enough of the selected TIP-20 fee token

-32000

Nonce too low

Transaction's nonce has already been used

-32000

Wrong subblock proposer

Type 0x54 transaction targets a subblock proposer different from this node

SDK Integration

Last updated

Was this helpful?