ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #solidity
Learn how to use Solidity's unchecked blocks to eliminate redundant overflow checks and reduce gas costs in high-frequency arithmetic operations.
Learn how Solidity custom errors replace expensive string reverts, reduce gas, and stay decodable by tooling. Includes a practical example, verification steps, and trade‑off discussion.
Deploy an ERC‑20 to Polygon’s zkEVM testnet, compare gas usage to Mainnet, and learn the trade‑offs of this early‑stage Layer‑2 solution. Get a step‑by‑step guide, key component overview, and actionable checklist for dApp teams.
Learn how immutable variables store constructor arguments in bytecode, lower gas reads, and avoid common pitfalls.
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.
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.
Vyper’s checked arithmetic and explicit reentrancy lock reduce common smart‑contract bugs. A minimal vault example shows how default safety can replace Solidity’s opt‑in libraries.
polygon
vyper