Skip to main content
Quantum Chain accepts the same transaction shapes as Ethereum: legacy, EIP-2930 (access list), and EIP-1559 (fee market). The only difference from Ethereum is the signature primitive — see Signing transactions.

Transaction fields

Build and broadcast a legacy transaction

Send via Qustody

If you use the Qustody platform, you do not build raw transactions yourself:
Qustody handles nonce assignment, fee estimation, signing orchestration, and broadcasting. Your application listens for transaction.broadcast and transaction.confirmed webhooks.

Fee estimation

Quantum Chain follows EIP-1559. Use:

Nonce management

The nonce is the count of transactions previously sent from the same address. Two rules:
  1. Nonces must be sequential. Skipping a nonce parks all later transactions in the queued pool until the gap is filled.
  2. Nonces from the latest mined block are returned by eth_getTransactionCount(addr, "latest"). To include pending transactions, use "pending".
If you submit transactions from multiple processes, coordinate nonces in a shared store, or route everything through Qustody (which serializes nonces per wallet).

Replacing or cancelling a stuck transaction

To replace a transaction that is stuck in the mempool:
  1. Submit a new transaction with the same nonce and a higher gasPrice (or maxFeePerGas and maxPriorityFeePerGas for EIP-1559).
  2. Both transactions race; the higher-fee one is mined.
To cancel, replace it with a self-transfer of zero value at a higher fee. Through Qustody, use POST /v1/transactions/{id}/cancel while the transaction is still in SUBMITTED, PENDING_AUTHORIZATION, APPROVED, or PENDING_SIGNATURE. After it has been broadcast, you must do a fee-bump replacement on chain.

Confirmation

A transaction is confirmed when its block is followed by enough additional blocks that a reorg is unlikely. Mainnet recommendations:

Where to go next