ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #solidity
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.
Should your contract accept Ether through receive() or a named payable function? A decision guide with a comparison table, trade-offs, and a validatable implementation pattern.
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.
Solidity 0.8.4+ custom errors replace string revert messages with typed errors, reducing gas costs and contract size. This article explains syntax, a worked example, gas comparisons, version limits, and common pitfalls.
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 Polygon PoS achieves EVM compatibility, allowing developers to deploy Ethereum smart contracts without code changes while balancing the trade-offs of sidechain security.
Learn how Solidity’s custom error feature replaces costly revert strings, lowers bytecode size, and keeps error information readable for off‑chain tooling. A worked example and trade‑offs are included.
polygon