A troubleshooting note from the TierZero team.
A signature returned by an RPC is not the same as a confirmed trade. Keep an execution record with the signed transaction, blockhash, lastValidBlockHeight, submission times, endpoint and observed status.
Before retrying
Primary reference: getLatestBlockhash
For a reproducible question, share sanitized errors and public signatures, never wallet secrets. Which failure state is your sender struggling to distinguish?
A signature returned by an RPC is not the same as a confirmed trade. Keep an execution record with the signed transaction, blockhash, lastValidBlockHeight, submission times, endpoint and observed status.
Before retrying
- Query signature status and preserve the error value. A missing result at one endpoint is not proof that execution never happened.
- Compare the relevant block height with the transaction validity boundary. Slots and block height are different counters; do not substitute a fixed wall-clock timer for the validity information.
- Check your commitment assumptions and whether providers are observing comparable chain state.
- Distinguish resending the same signed payload from signing a replacement. A replacement can represent a second economic action if the earlier attempt landed.
Primary reference: getLatestBlockhash
For a reproducible question, share sanitized errors and public signatures, never wallet secrets. Which failure state is your sender struggling to distinguish?