ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #solidity
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.
Learn how to prevent reentrancy attacks in Solidity using the Checks-Effects-Interactions (CEI) pattern to ensure contract state is updated before external calls.
A step‑by‑step guide to migrate Solidity contracts from revert strings to custom errors, covering declaration, replacement, ABI updates, testing, and gas verification.
Learn how to distinguish between actual funding shortages and masked Solidity reverts when encountering 'Insufficient funds' and 'Gas estimation failed' errors in Hardhat.
Learn how to prevent reentrancy attacks in Solidity using the Checks-Effects-Interactions (CEI) pattern to ensure contract state is updated before external calls.
Learn how to implement the Pull Payment pattern in Solidity to prevent Denial of Service (DoS) attacks and ensure secure fund distribution by shifting transfer risks to the recipient.
Since Solidity 0.5.0, the compiler rejects any function declared without an explicit visibility specifier. Before that release, a missing keyword silently defaulted to public — a classic route to accidental external access. Function visibility is now mandatory, but the neighboring state-variable decision remains open. State variables default to internal, yet
Learn how Solidity’s unchecked { } blocks let you skip overflow checks after proper validation, cutting gas costs in loops and math‑heavy functions while keeping contracts safe.