ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to replace revert reason strings with Solidity custom errors (since 0.8.4) to cut deployment costs, keep revert semantics, and enable typed error data that off‑chain tools can decode.
Immutable variables let Vyper contracts embed constants in bytecode, cutting read costs and storage use. This post explains how they work, shows a real example, highlights trade‑offs, and tells you how to verify the savings in your own project.
Learn how Solidity custom errors (since 0.8.4) cut deployment size, provide typed revert data, and simplify testing—complete with a token‑gated example, trade‑offs, and verification steps.
Solidity's immutable keyword eliminates constructor storage writes and turns reads into cheap immediate loads. This post shows a fee-collector example, measures ~45k gas saved on deployment, and outlines when immutability is the wrong choice.
Solidity custom errors (0.8.4+) give you typed, ABI-decodable, gas-cheaper failures than revert strings. Here's the syntax, a worked Foundry test, and the real trade-offs.
Learn how Solidity 0.8+ handles integer overflows, when to use unchecked blocks for gas savings, and where protection fails.
Solidity custom errors (v0.8.4+) replace revert strings with a 4‑byte selector and typed arguments, cutting bytecode size and gas on failure.
Custom errors replace revert strings with typed, named parameters — saving ~500–800 gas per revert. Declare them in a shared file, trigger with revert ErrorName(args), and frontends decode automatically via the ABI. Includes a worked token example, gas comparison table, and verification steps.
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.
solidity
vyper