Transaction management automates tasks related to:
- Creating transactions, including crafting transaction data, managing gas, managing nonces, and signing transactions.
- Sending transactions to a chain.
- Post-processing mined transactions, including catching receipts and decoding event logs.
Orchestrate handles nonce assignment internally enabling the maximal theoretical throughput in transactions per second (TPS) for a single account.
Use the SDK or HTTP REST API to send transactions. Sending transactions generates and sends protobuf messages to Apache Kafka. Orchestrate receives the protobuf messages and manages the full transaction lifecycle.
Set transaction priority
Orchestrate allows you to set the transaction priority if a gas price is not specified. Use the SDK or REST API to set the transaction priority when submitting the transaction.
Do not specify a priority on networks that enforce a minimum gas price. This ensures the user does not submit a low priority transaction where the transaction’s gas price is lower than the minimum accepted by the Ethereum client.
The following priorities are available:
- Very high; 1.4 x gas price
- High; 1.2 x gas price
- Medium; 1 x gas price (default)
- Low; 0.8 x gas price
- Very low; 0.6 x gas price