Smart contract development best practice

VeChainThor Solidity The Right Way

Motivation

As you may know, EVM is also the runtime environment for smart contracts in VeChainThor. So this guide is built upon and inspired by a number of articles and talks by the Ethereum community. These practices are certainly not unique to programming and development in VeChainThor.

Our goal here is to make you a better—more effective, more knowledgeable, more practical—solidity developer in VeChainThor.

General Philosophy

• Keep Simple: Complexity increases the likelihood of errors.
• Security First: The security of a smart contract is always a top priority.
• Revert As Far As Possible: Do not use return false when a condition is not met.

Contents:

• Recommendations
  • Protocol specific recommendations
  • Solidity specific recommendations
• Design Patterns
  • Behavioral Patterns
  • Security Patterns
  • Upgradeability Patterns
  • Economic Patterns
• Security
  • Reentrancy
  • Pitfalls in Reentrancy Solutions
  • Front-Running (AKA Transaction-Ordering Dependence)
  • Timestamp Dependence
  • Integer Overflow and Underflow
  • DoS with (Unexpected) revert
  • DoS with Block Gas Limit
  • Forcibly Sending VET to a Contract
• Resources
  • Tools
  • Libraries
  • Links