eth_sendRawTransaction

eth_sendRawTransaction submits an already-signed transaction to Polygon mainnet for inclusion in a block. You sign the transaction locally with your private key, RLP-encode it, hex-encode the result, and pass that single 0x-prefixed hex string as the only parameter. Triport never sees or holds your key — only the signed payload.

On success the method returns the transaction hash immediately. The hash is returned as soon as the transaction is accepted into the mempool; it does not mean the transaction has been mined. Polygon's Bor consensus produces blocks roughly every ~2 seconds, so poll eth_getTransactionReceipt — or the transaction-by-hash lookups — with the returned hash to confirm inclusion and read the final status.

This is the only state-changing method on the Polygon eth surface, and it sits in its own polygon_send_tx rate-limit category with markedly lower limits than read methods (3 rps on free vs. 15 rps for reads). Budget your send rate accordingly and back off on -32003. The method is available from the free tier upward — no paid tier is required to broadcast transactions.

Gotchas

• Use Polygon's chain ID. The transaction must be signed with EIP-155 replay protection using chain ID 0x89 (137). A transaction signed for another chain (e.g. Ethereum mainnet, 0x1) is rejected with -32000 invalid sender before it ever reaches the mempool, because the recovered signer does not match.
• Replay protection is mandatory. Without EIP-155 binding to 0x89, a Polygon transaction could also be valid on other EVM chains — a replay-attack vector. Always sign with the correct chain ID.
• Idempotent re-broadcast. Re-submitting the same signed transaction (same hash) is safe. Depending on the upstream node it returns either the same hash again or -32000 already known. Treat both outcomes as success.