Migrating Solidity Reverts to Custom Errors: A Practical Guide
Replace require strings with Solidity custom errors (0.8.4+): declaration, revert syntax, Foundry/ethers decoding, gas verification, and migration pitfalls.
Loading…
ReadMeFeed / Community knowledge
#gas-optimization
Real questions. Useful conversations. Find the people who know your stack.
solidityUsing Solidity Custom Errors for Gas‑Efficient Reverts
Learn how Solidity custom errors (since 0.8.4) replace costly revert strings with cheap, typed data, saving gas while keeping error messages readable off‑chain.
Using Vyper Immutable Variables to Save Gas on Configuration Values
Learn how Vyper’s immutable variables embed configuration values in creation code to avoid costly SLOAD reads, with a worked token example and deployment verification steps.
vyperSolidity Libraries: When Delegatecall Saves Gas and When It Burns You
Solidity libraries cut bytecode via delegatecall, but they run in the caller's storage context—creating silent corruption risks when layouts diverge. A worked example shows how a nonce library breaks when a mapping shifts slots, plus gas numbers to decide when libraries actually pay off.
Using Solidity Immutable Variables to Cut Gas and Boost Security
Learn how declaring never‑changed state variables as immutable removes storage writes, lowers gas costs, and prevents accidental mutation, with a concrete ERC‑20 example and verification steps.
Replacing Revert Strings with Custom Errors in Solidity: A Practical Migration Guide
Replace revert strings with Solidity custom errors (0.8.4+) to shrink bytecode and cut revert gas. Covers the conversion pattern, test updates, gas verification, and tooling caveats.
Optimizing Smart Contract Reverts with Solidity Custom Errors
Learn how to replace expensive string-based reverts with Solidity custom errors to reduce gas costs, improve ABI decoding, and implement typed error handling.
Optimizing Gas Costs with Solidity Immutable State Variables
Learn how to use Solidity's immutable state variables to reduce SLOAD gas costs by embedding data directly into contract bytecode during deployment.
Solidity 0.8.x Gas Optimization: Calldata vs Memory for Read-Only Arguments
When designing smart contracts for low-traffic workloads, minimizing gas expenditure during function execution is a priority. Solidity 0.8.x provides different data locations for function parameters, specifically memory and calldata . While calldata is documented as a non-modifiable, non-persistent area where function arguments are stored, the specific gas t