ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Solidity’s `unchecked` block lets you skip automatic overflow checks for gas savings, when it’s safe to use, and a practical token transfer example that shows the trade‑offs and how to audit the code.
Replace require strings with Solidity custom errors (0.8.4+): declaration, revert syntax, Foundry/ethers decoding, gas verification, and migration pitfalls.
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.
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.
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.
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.
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.
Learn how to replace expensive string-based reverts with Solidity custom errors to reduce gas costs, improve ABI decoding, and implement typed error handling.
Learn how to use Solidity's immutable state variables to reduce SLOAD gas costs by embedding data directly into contract bytecode during deployment.
solidity
vyper