What would Solidity look like if it was built today?
summary
Proposes a Solidity redesign that pushes runtime checks to compile time: payable as an annotation enforced by the compiler, ecRecover returning a Result/unwrap instead of the zero address, and local bindings with right-side types via a let keyword. Shows a concrete implementation called Sway that compiles to its own VM, argues this reduces optimizer-driven gas hacks and class of bugs like unchecked ecRecover, and demonstrates standard-library intrinsics and explicit error handling that convert silent failures into automatic reverts.
AI-written summary · about
chapters (3)
related talks
37mExperimental Solidity
20mSolidity's most common security pitfalls and its best safeguards
41mBattle of the Languages
23mHow Type-Driven Development Can Turbocharge your Contract's Security
38mIntroducing Core Solidity
12mPlank: The New Best Way to Develop Smart Contracts
25msolx: an LLVM-based Solidity toolchain
20mSlang Building Solidity Compiler APIs from a Declarative Language Specification