Transaction lifecycle
An RPC submission moves a signed transaction into a bounded pool. Execution and finality happen later.
Transaction families
Ethereum tools submit legacy, EIP-2930 access-list and EIP-1559 dynamic-fee envelopes through eth_sendRawTransaction. Native JZTX transactions use joltzu_sendRawTransaction. Both enter the same execution/consensus pipeline; the byte formats are different.
The node does not store wallet keys or sign transactions. Obtain the chain ID, pending nonce, fee suggestion and gas estimate; sign outside the node; submit the signed bytes.
Admission and rollback
Admission checks chain, signature, nonce, gas, fee and pool bounds. The pool refuses any transaction whose gas limit is above 1,000,000, its per-simulation candidate budget, even though eth_call and eth_estimateGas accept up to 16,777,216. A returned hash does not reserve a balance or promise propagation/inclusion. Duplicate pending submission can return the same hash.
A failed execution rolls back its EVM/native changes and logs. Transaction nonce consumption and gas charges remain subject to the outer runner rules. Atomic plans roll back their component execution effects together; they do not waive outer gas fees.
A top-level value transfer refused by a lock, fund energy or an outflow budget is an exceptional failure that pays its full gas limit, because admission checks only the balance net of the fee reservation. Inside a call, a refused transfer fails before any code runs and the caller keeps the gas it forwarded.
The development fee profile has zero base fee. For dynamic-fee envelopes, the effective price is constrained by the fee cap and priority fee. Suggestions are development heuristics, not a network minimum or future pricing promise.
Two block identifiers
Ethereum RPC uses the Ethereum header hash: keccak(rlp(header)). Native proof RPC uses the Joltzu certified block identifier. The Ethereum header's extraData carries the 32-byte Joltzu identifier. Do not interchange the two in selectors or proof verification.
Read Ethereum RPC for field differences and proofs for trust requirements.