SubmitTransaction

Broadcast a fully signed transaction to the Solana network.

Broadcasts a fully signed transaction to the Solana network. Returns a submission result and transaction signature immediately — it does not wait for on-chain confirmation.

SUBMISSION_RESULT_SUBMITTED means the transaction was accepted for broadcast, not that it was confirmed or executed on-chain. The transaction may still be dropped, fail during execution, or expire.

Always use MonitorTransaction after submission to track actual on-chain status.

Request

transaction · Transaction (object) · required

Fully signed transaction in FULLY_SIGNED state.

Show Transaction fields

state · TransactionState (enum)

Must be TRANSACTION_STATE_FULLY_SIGNED (4). Submit will fail if any required signatures are missing.

commitment_level · CommitmentLevel (enum)

Optional. Controls the confirmation target used when monitoring submission. Defaults to COMMITMENT_LEVEL_CONFIRMED.

Response

signature · Base58-encoded string

Transaction signature. Use this value with MonitorTransaction to track on-chain status. Present even for some failure cases.

submission_result · SubmissionResult (enum)

Whether the transaction was accepted for broadcast. See the SubmissionResult table below.

error_message · string

Human-readable error description if submission failed. Empty on success.

structured_error · TransactionError (object)

Structured error for programmatic handling. Present when submission failed or the result is indeterminate. See Error Reference for TransactionErrorCode values.

Show TransactionError fields

code · TransactionErrorCode (enum)

Specific error code. See Error Reference for the full list.

message · string

Human-readable error message.

retryable · bool

True if the same transaction might succeed if retried without modification.

certainty · TransactionSubmissionCertainty (enum)

How certain we are about whether the transaction was submitted. Critical for INDETERMINATE results.

blockhash · string

The transaction’s blockhash.

blockhash_expiry_slot · uint64

Slot when the blockhash expires. Use this to determine when it’s safe to check on-chain whether the transaction was submitted.

SubmissionResult Values

Result	Value	Meaning
SUBMISSION_RESULT_UNSPECIFIED	0	Not set.
SUBMISSION_RESULT_SUBMITTED	1	Transaction broadcast to the network. Not a confirmation. Use MonitorTransaction to track.
SUBMISSION_RESULT_FAILED_VALIDATION	2	Pre-submission validation failed. The transaction was not sent.
SUBMISSION_RESULT_FAILED_NETWORK_ERROR	3	Network or RPC error prevented submission. The transaction was likely not sent.
SUBMISSION_RESULT_FAILED_INSUFFICIENT_FUNDS	4	Fee payer has insufficient SOL. The transaction was not sent.
SUBMISSION_RESULT_FAILED_INVALID_SIGNATURE	5	Signature validation failed. The transaction was not sent.
SUBMISSION_RESULT_INDETERMINATE	6	Unknown state. Check structured_error.certainty and structured_error.blockhash_expiry_slot to determine the recovery strategy.

For SUBMISSION_RESULT_INDETERMINATE: wait until after blockhash_expiry_slot, then query the blockchain. If the transaction is not found on-chain by then, it is safe to recompile and resubmit. See Error Reference for TransactionSubmissionCertainty handling guidance.

Code Examples

Go

resp, err := client.SubmitTransaction(ctx, &transaction_v1.SubmitTransactionRequest{
    Transaction: signedTxn,
})
if err != nil {
    log.Fatal(err)
}
fmt.Printf("Signature: %s\n", resp.Signature)
fmt.Printf("Result: %v\n", resp.SubmissionResult)

if resp.SubmissionResult == transaction_v1.SubmissionResult_SUBMISSION_RESULT_SUBMITTED {
    // Use MonitorTransaction to track on-chain status
    fmt.Println("Submitted — use MonitorTransaction to confirm")
}