Solana Transaction Dropped With No Error: The Seven Doors
Originally published on xroot.dev . The worst outcome on Solana is not a failed transaction. A failed transaction tells you what went wrong: the log says slippage, or insufficient funds, or a program error, and you fix it. The worst outcome is the one where you sign, the wallet says "sent", and a minute later the signature does not exist. No error, no log, no fee charged, no explanation. That…
The most dire outcome in the Solana blockchain is not a failed transaction, but one that slips through the cracks without any trace. There are seven distinct causes for this mysterious disappearance, each governed by specific rules.
Door One occurs when a leader's buffer is nearly full, discarding any incoming transaction below the current priority threshold. The priority is determined by the ratio of fee to requested block space, not the fee itself. Right-sizing this limit can help avoid this issue.
Door Two involves a two-second memory that discards duplicate transactions. If a packet arrives within two seconds of the previous one, it is dropped. To circumvent this, resend after a two-second wait or as a new transaction with a different blockhash.
Door Three is related to the RPC connection. Leaders prioritize transactions based on the sender's stake, with unstaked nodes receiving only 128 concurrent streams while staked nodes can have up to 512. Transactions from unstaked nodes may be dropped if the RPC provider routes them through an unstaked node.
Door Four is about the forwarding capability of non-leader nodes. They can forward transactions to the next few leaders, but only if the original packet came from a staked node. This forwarded transaction is discarded unless the leader is within 20 slots (about 8 seconds).
Door Five concerns the retry service's limits. If an RPC node holds more than 10,000 transactions in its retry pool, new transactions are sent once and then forgotten. Transactions that fail on-chain are immediately removed from the pool, while those that have not been rooted are retained for potential resending.
Door Six is about the inability to reach the leader in time. Direct-to-leader transactions open QUIC connections to upcoming leaders. If a leader does not complete the handshake within 2 seconds, the sender waits another 1.6 seconds before retrying. This delay can cause the transaction to miss its window.
Door Seven is about the block being full in an unseen manner. A block has four ceilings: total compute units, writable accounts, new account data, and entries. If a transaction exceeds any of these limits, it is held until the next block. A hot pool with already absorbed 24 million compute units will cause all transactions writing to it to wait, and after 150 slots, the transaction is lost if it cannot land in the next block.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
