Solidity 0.8.20 unchecked Block: Storage Variable Overflow Semantics Remain Undefined

Answer the Question

In Solidity 0.8.20 the unchecked block suppresses overflow checks for *local* arithmetic, but the language reference marks storage‑variable overflow inside an unchecked block as implementation‑dependent. The current compiler (solc 0.8.20) writes the result of an overflowing arithmetic expression directly to storage, which the EVM performs with wrap‑around semantics. However, this behavior is not guaranteed to persist in future compiler releases or across EVM implementations.

Confirmed Facts

• solc 0.8.20 emits EVM arithmetic on storage writes inside unchecked blocks, producing wrap‑around on overflow.
• The spec explicitly labels storage overflow in unchecked as implementation‑dependent.
• Solidity 0.9.0 release notes indicate an upcoming clarification of unchecked semantics for storage variables.
• Auditors should treat unchecked storage writes as a potential finding until the spec is updated.
• Using unchecked on storage writes can trigger a revert guard if the target variable is marked immutable or constant.

Recommended Pattern for Gas‑Saving Storage Arithmetic

1. Keep unchecked blocks only around local variable calculations.
2. Perform the storage write in a separate statement after the arithmetic.
3. Alternatively, use inline assembly to enforce deterministic wrap‑around:

   assembly {
       let newVal := add(sload(slot), 1)
       sstore(slot, newVal)
   }

4. Verify the assembly path on the target EVM, as opcode behavior may differ.
5. Document the intent in the code comments and include a unit‑test that triggers an overflow to confirm wrap‑around.

What to Ask the Developer

To choose the safest pattern, confirm whether any of the affected storage variables are declared immutable or constant. If so, a revert guard may be inserted by the compiler even inside an unchecked block, making wrap‑around unreliable.

Audit Recommendation

Until Solidity 0.9.0 finalizes the semantics, auditors should flag any use of unchecked that writes to storage as a finding. The flag should include a note that the behavior is currently implementation‑dependent and may change with future compiler releases.