eth_sendRawTransaction — Base JSON-RPC

Submit a signed raw transaction.

Scope: base:rpc

Params schema

JSON

parser_only

[
  {
    "name": "rawTransaction",
    "required": true,
    "schema": {
      "$ref": "#/components/schemas/BaseR03_raw"
    }
  }
]

Result schema

JSON

OpenRPC

{
  "name": "result",
  "schema": {
    "$ref": "#/components/schemas/BaseR03_hash"
  }
}

Parameter limits

JSON path	Frozen limit	Source
—	`unknown`	No numeric parameter ceiling is frozen; enforce the declared schema shape and deny an unknown oversized/range profile.

Historical block retrieval is not an archive-state guarantee. Selectors must be preserved; do not substitute pending, safe, or finalized with latest.

Rate limits and tier

These are enforced product-policy values, not measured upstream capacity or an SLA. Enterprise is finite, never physical “unlimited” capacity.

Tier	Limit / access	Category
Free	3 RPS sustained · up to 6 burst	base_send_tx
Basic	5 RPS sustained · up to 10 burst	base_send_tx
Pro	30 RPS sustained · up to 60 burst	base_send_tx
Business	80 RPS sustained · up to 160 burst	base_send_tx
Enterprise	80 RPS sustained · up to 160 burst	base_send_tx

See Base limits and Burst capacity. The included buffer refills at sustained RPS; there is no quota on the number of bursts.

Errors

Code	Meaning here	Client action
`-32602`	Parameters fail the declared schema or upstream parser.	Fix the positional parameters; parser acceptance is not execution success.

Tier and budget rejections are not JSON-RPC errors: the gate decides them before the request reaches the RPC layer and answers with a plain HTTP envelope — 403 tier_insufficient (with an X-Required-Tier header) or 429 rate_limited (honor Retry-After). Both are enforced product policy, not measured capacity or an SLA.

Authentication/transport failures use the shared client error envelope. See Base errors.

Evidence

Fixture kind: parser_only.
Fixture source: infra-4-sety/integration-base/research/R00/import/originals/probe/bse_f20_submitmap.json at /results/0.
Fixture SHA-256: 6e248b7fb9476d6152eed911ae535cf1bf43be7e9b83a2267feaf02ba9abde51.
Fixture registry: infra-4-sety/integration-base/research/R00/import/FIXTURES_INDEX.json.
Semantic assertion: HTTP 400, -32602 rlp rejection; never accepted send.
Evidence boundary: Replay only this bounded assertion; no provider calls or original Python execution. Metadata/response fragments can test rejection but cannot prove capability.

Limitations

Keyed originator endpoint; provider forwarding/searcher disclosure is not private method proof.
Availability is the frozen baseline, not deployed readiness. documented is the contract floor; evidence_kind retains unknown/source_summary.