Solana JSON-RPC proxy (sendTransaction)

JSON-RPC 2.0 proxy mirroring Solana's HTTP RPC sendTransaction method. The signed transaction is forwarded to the LP-Agent priority RPC and the signature is returned as soon as the priority RPC accepts it (the rotating RPC pool is fanned out to in the background). The client is responsible for polling confirmation.

Upstream spec: https://solana.com/docs/rpc/http/sendtransaction

Parameters

params is a positional tuple — order matters.

Index	Type	Required	Description
params[0]	string	yes	Fully-signed Transaction, encoded as a string (see encoding below).
params[1]	object	no	Configuration object (see SendTransactionConfig schema).

Configuration object (params[1])

Field	Type	Default	Description
encoding	string	base58	base58 (DEPRECATED upstream) or base64.
skipPreflight	boolean	false	When true, skip preflight transaction checks.
preflightCommitment	string	finalized	Commitment level for preflight (processed \| confirmed \| finalized).
maxRetries	integer	—	Max retries by the RPC node. If omitted, retries until blockhash expires.
minContextSlot	integer	—	Minimum slot at which to perform preflight checks.

Result

A JSON-RPC 2.0 envelope whose result is the first transaction signature (base58) embedded in the submitted transaction — i.e. the transaction id. HTTP status is always 200 per JSON-RPC 2.0; on failure, the envelope contains an error field instead of result.

Request body

jsonrpc'2.0' required

method'sendTransaction' required

Example request

{
  "id": 1
}

Response

JSON-RPC response (success or error envelope). HTTP is always 200; inspect result vs error.

jsonrpc'2.0' required

resultstring

First transaction signature embedded in the submitted transaction, base58-encoded.

Example response

{
  "id": 1,
  "result": "2id3YC2jK9G5Wo2phDx4gJVAew8DcY5NAojnVuao8rkxwPYPe8cSwE5GzhEgJA2y8fVjDEo6iR6ykBvDxrTQrtpb",
  "error": {
    "code": -32602,
    "message": "Invalid params"
  }
}