Optimizing Gas Costs with Solidity Immutable State Variables
Learn how to use Solidity's immutable state variables to reduce SLOAD gas costs by embedding data directly into contract bytecode during deployment.
Loading…
ReadMeFeed / Community knowledge
#evm
Real questions. Useful conversations. Find the people who know your stack.
soliditySeparate HTTP and WebSocket Providers in Web3.js v4 for Reliable Reads and Events
Use HttpProvider for eth_call reads and WebSocketProvider for log subscriptions in web3.js v4. Bind the ABI once with web3.eth.Contract and route reads and events separately for reliability.
web3jsSolidity 0.8.x Gas Optimization: Calldata vs Memory for Read-Only Arguments
When designing smart contracts for low-traffic workloads, minimizing gas expenditure during function execution is a priority. Solidity 0.8.x provides different data locations for function parameters, specifically memory and calldata . While calldata is documented as a non-modifiable, non-persistent area where function arguments are stored, the specific gas t
REVERT rolls back state, but a retried transaction still writes twice — where should idempotency live?
REVERT and the retry gap I understand that when a state-changing call ends in REVERT , the EVM rolls back that transaction's storage writes, so a single confirmed transaction either commits fully or not at all. What I am trying to resolve is the retry path: a client that does not see a receipt in time may build a new transaction (new nonce) for the same logi