Plank: The New Best Way to Develop Smart Contracts
summary
Plank presents a small-core smart-contract language with an extensible standard library that implements ABI encoding and reusable EIP-712 patterns instead of baking them into the compiler. The prototype compiler emits real EVM bytecode, compiles conservatively over 40× faster than Solidity, shows gas overhead near 1% on many benchmarks, and already attracts 11 independent contributors. Version 0.2, next-gen codegen, and a plan for formal verification aim to reduce low-level manual optimizations.
AI-written summary · about
chapters (21)
- 0:00Introduction to Plank EVM
- 0:28Five Years Building With Solidity
- 1:01Developer and Auditor Friction
- 1:29Repeated Footguns and Missing Tests
- 1:58How Weak Tooling Raises Audit Costs
- 2:40Solidity Extensibility Limits
- 3:00Missing Generics and Metaprogramming
- 3:15Security Problems in Basic Building Blocks
- 4:04Slow Evolution of the Solidity Language
- 4:36How Optimization Caused a Vulnerability
- 5:29What the Solidity Compiler Contains
- 5:52Comparing Rust, Zig, and Python
- 6:19Moving Features Into Standard Libraries
- 7:12Shrinking the Core With Plank
- 7:42An Extensible Smart Contract Stack
- 8:28Reusable EIP-712 Implementations
- 9:27Compiler Speed and Gas Benchmarks
- 10:05Plank Version 0.2 Roadmap
- 10:28Next-Generation Compiler Improvements
- 10:49Formally Verifying the Compiler
- 11:23Closing Resources for Plank Developers
related talks
37mExperimental Solidity
37mSolidity in 2022: Recent and Planned Features
41mBattle of the Languages
08mA brief history of "smart contracts"
38mIntroducing Core Solidity
15mWhat would Solidity look like if it was built today?
01h 25mSpeculation in Smart Contracts
20mSlang Building Solidity Compiler APIs from a Declarative Language Specification