Seven Silent Ways Solana Drops Your Transaction Without Any Error or Log
On Solana, a transaction can disappear after being signed and sent, with no error message, no fee charged, and no log entry to explain what happened. There are seven distinct points in a validator's pipeline where a transaction can be silently discarded, each governed by specific technical thresholds. These include a congestion-based priority floor that kicks in when the leader's 100,000-transaction buffer hits 99% capacity, a bloom filter that drops duplicate or falsely flagged packets within a two-second window, and QUIC connection limits that restrict unstaked RPC nodes to just 128 concurrent streams. Additional silent failures can occur during peer forwarding, where packets from unstaked or already-forwarded nodes are rejected, and within RPC retry pools that abandon transactions once the 10,000-entry limit is exceeded. Understanding each failure point allows developers to adjust compute unit limits, retry timing, and RPC infrastructure to improve transaction delivery without changing the underlying logic.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in