ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
This architecture note outlines how Reach enforces token balance safety at compile time using linear types and SMT‑based verification, covering requirements, minimal design, trust boundaries, operational checks, limitations, and triggers for design change.
Learn how to implement persistent state in Cairo using the Storage trait and StorageMap. This guide covers the implementation of a counter contract and the verification process using Scarb and Starkli.
Learn how Vyper's default overflow protection and strict bounds checking eliminate common smart contract vulnerabilities by moving safety from the library level to the compiler level.
Learn how to prevent reentrancy attacks in Solidity using the Checks-Effects-Interactions (CEI) pattern to ensure contract state is updated before external calls.
Explore how Vyper's bounded loop requirement prevents gas-based DoS attacks by enforcing compile-time limits on all iterations, prioritizing security over Turing-completeness.
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.
Context When securing state-changing external functions in Vyper against reentrancy, two documented patterns exist: the built-in @nonreentrant decorator and a manually managed boolean state variable. The decorator reserves a storage slot and reverts on reentry, while a manual guard offers custom revert or skip logic but demands discipline across every exit p
Learn how to implement Custom Gas Tokens on Polygon to allow users to pay transaction fees with assets other than POL, reducing onboarding friction.
Learn how to handle asynchronous smart contract interactions in Web3.js, distinguishing between .call() and .send(), and implementing event listeners to keep your UI in sync with the blockchain.
cairo
vyper
solidity
polygon
web3js