Solana accepts SIMD-0582: fail on trace overflow before doing the work
Victoria Shinder2 min readSIMD-0582, "Early detection of instruction trace overflow", was merged into Solana's improvement documents repository on 16 September 2026. Pull request #582 came from LucasSte, ran to six commits and 38 comments in discussion, and adds 134 lines in a single file. The merge was performed by the repository's simd-bot.
The instruction trace is the record of instructions a transaction executes, including the cross-program invocations a program makes as it runs. It is bounded: a transaction may only go so deep and so wide before the runtime refuses to continue.
The proposal is about when that refusal happens rather than whether it does.
What it means
Failing early is a cheaper way to fail. If a transaction is going to exceed the trace limit, every instruction executed before the limit is reached is work the validator performed for a transaction that was always going to be rejected. Detecting the condition before that work begins removes it from the block's budget, and the beneficiary is not the failing transaction but every other transaction competing for the same slot.
There is a second effect that matters more for anyone writing programs. A limit enforced late produces an error at an arbitrary depth of a call chain, which is the hardest kind of failure to attribute: the instruction that reported the error is rarely the one that caused it. A limit checked up front gives a determinate answer about the transaction as submitted.
⚠️ Status, precisely. A merged SIMD is an accepted specification, not a shipped change. It becomes real in a validator client release and, where required, a feature gate activated on mainnet. This note describes what the repository shows — the title, the author, the size of the change and the discussion around it — and we have not reviewed the specification text itself.
Nothing here is investment information.