Web3.js Contracts: Call vs. Send and the 1.x to 4.x Migration Shift
Understanding web3.eth.Contract: when to use .call() vs .send(), how to handle event logs with chunked queries, and the breaking changes from web3.js 1.x to 4.x.
Loading…
ReadMeFeed / Community knowledge
#smart-contracts
Real questions. Useful conversations. Find the people who know your stack.
web3jsWhy Clarity Contracts Behave the Same on Every Stacks Node
Clarity enforces deterministic smart contract execution on Stacks through a decidable stack machine, enforced read/write boundaries, and statically known gas costs — here's how that works and what it costs you.
clarityreceive() or a Named Payable Function? A Solidity Ether-Handling Decision Guide
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.
solidityUsing Vyper Immutables for Gas‑Efficient, Unchangeable Contract Parameters
Vyper’s immutable variables let you store constants on‑chain without the cost of regular storage reads. This blog explains how they work, shows a concrete example, compares gas usage, and discusses when immutables are the right choice.
vyperChoosing Between Local Hardhat Network and Mainnet Forking for Smart Contract Tests
A decision guide for Ethereum testing: when to use Hardhat's fast in-memory network versus a forked mainnet, with config, a validation test, and the operational trade-offs.
hardhatCairo 1 Storage: Declarative #[storage] vs Manual StoragePointer — A Decision Guide
A decision guide for Cairo 1 StarkNet contracts: when to use the declarative #[storage] struct versus manual StoragePointer access, with trade-offs, example code, and validation steps.
cairoSolidity Libraries: When Delegatecall Saves Gas and When It Burns You
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.
Diagnosing and Fixing Reentrancy in Vyper with @nonreentrant
Diagnose reentrancy in Vyper: identify risky external calls, apply @nonreentrant locks with proper keys, and verify with a simple attacker test. Follow the step‑by‑step guide to secure your smart contracts.
Clarity's Recursion Trap: Why Your Contract Needs Depth Guards Before Mainnet
Clarity bans loops to keep execution costs predictable — which means recursion without a depth guard is a mainnet incident. Here's how to bound your contract logic and verify it before deployment.