ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #vyper
Learn how Vyper’s language design forces loops to have compile‑time known limits, preventing out‑of‑gas attacks and making contract gas costs predictable.
An architecture note on where Vyper's @nonreentrant lock belongs: which functions need it, why checks-effects-interactions is still required, and how to verify the lock with a hostile receiver contract.
Developers want to use Vyper’s block.timestamp to trigger contract logic based on a specific regional time zone, such as executing a function at 09:00 local time each day. Because block.timestamp returns UTC epoch seconds and Vyper provides no native timezone‑aware conversion functions, the implementation must rely on custom arithmetic or external libraries,
We operate a set of Vyper contracts behind an externally managed proxy pattern (the language itself has no delegatecall or proxy support), and we are defining a recovery procedure for a failed implementation swap. The contracts were originally compiled under Vyper 0.3.x with a pragma vyper directive, and the new implementation targets 0.4.x. The unresolved d
Goal I need a Vyper external function to return a struct that a Solidity caller decodes with abi.decode on a live chain. Tests may pass locally when both contracts are compiled with the same Vyper version, but production uses a Solidity consumer. Constraints Vyper 0.2.x and 0.3.x encode structs in a tightly packed format that omits padding between elements.
Vyper creates an external read-only getter for any state variable declared public and treats functions as external by default. The internal modifier must be added explicitly to keep helper logic from being callable externally. The goal is to understand the documented capability limits around accidental exposure: when a public variable is used unintentionally
Vyper’s compiler currently produces concise error messages that often omit contextual details needed by novice developers to understand verification failures. The language deliberately excludes user‑defined types such as structs, and community discussion questions whether introducing structured data could clarify errors while maintaining Vyper’s security‑fir
Vyper enforces strict bounded loops to ensure that iteration counts are determinable at compile-time, preventing potential out-of-gas attacks and maintaining deterministic bytecode mapping. While this constraint ensures safety, the interaction between nested bounded loops and evolving EVM gas pricing models introduces uncertainty. Specifically, as the EVM ev
The goal is to determine whether contracts written for Vyper 0.2.x that use the `constant` keyword can be recompiled under Vyper 0.3.0 or later without changing their on-chain storage layout or read behavior. In Vyper 0.2.x, `constant` declares immutable state variables backed by storage slots. Starting with Vyper 0.3.0, `constant` is no longer recognized; v
solidity