TierZero implementation note.
Track submission, inclusion and the business outcome as separate states. A transaction hash is useful for correlation; it is not the final answer to whether a swap succeeded.
Receipt and state checklist
Primary reference: Ethereum JSON-RPC documentation
Post sanitized receipts and expected outcomes when asking for help, not signing keys.
Track submission, inclusion and the business outcome as separate states. A transaction hash is useful for correlation; it is not the final answer to whether a swap succeeded.
Receipt and state checklist
- Fetch the receipt and inspect status, block identity and the expected contract logs. A null receipt can mean it is not available yet.
- Decode events from the contract addresses your integration expects. An event with a familiar name is not sufficient on its own.
- Apply a confirmation/finality policy suitable for the target network and handle a receipt changing after a reorganization.
- Reconcile token amounts and fees using the intended accounting model; gas used is not the whole economic result.
- Handle nonce replacement and retries without recording two fills for one action.
Primary reference: Ethereum JSON-RPC documentation
Post sanitized receipts and expected outcomes when asking for help, not signing keys.