Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/problem_statement.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The decentralized web needs a lingua franca that will allow platform creators to
2. **Smart contract languages aren't safe enough.**
Multimillion dollar exploits are a [regular](https://rekt.news/) occurrence.
Effective smart contract developers must be experts in both security and their product.
Language design mistakes (e.g., [re-entrancy](https://consensys.github.io/smart-contract-best-practices/attacks/reentrancy/), insufficient access control features, [silent integer overflow](https://consensys.github.io/smart-contract-best-practices/attacks/insecure-arithmetic/)) increase the attack surface for contracts, make audits expensive and slow, and frustrate the adoption of formal verification.
Language design mistakes (e.g., [re-entrancy](https://scsfg.io/hackers/reentrancy/), insufficient access control features, [silent integer overflow](https://consensys.github.io/smart-contract-best-practices/attacks/insecure-arithmetic/)) increase the attack surface for contracts, make audits expensive and slow, and frustrate the adoption of formal verification.
We believe that insufficient language safety is a serious barrier to both mainstream adoption of digital assets and accessible smart contract development.

3. **Smart contract execution layers aren't fast.**
Expand Down