Smart Contracts from the Trenches – The Interface App Journey
Download as PPTX, PDF1 like122 views
The document outlines best practices for developing smart contracts, emphasizing the use of vetted libraries, minimizing on-chain storage, and ensuring flexibility in design. Key recommendations include creating access controls, using SafeMath for arithmetic safety, and avoiding loops to prevent gas limit issues. Overall, it suggests a proactive approach to contract design with an emphasis on configurability and effective event management.
Smart Contracts from the Trenches – The Interface App Journey
- 1. Smart Contracts From The Trenches: The Interface App Journey Nik KALYANI Co-founder/CTO @techbubble
- 5. 1. Don’t reinvent Use vetted libraries such as OpenZeppelin
- 6. 2. Minimize on-chain storage Store only what’s really needed on the blockchain. Hashes are your friend.
- 7. 3. Build-in configurability Things change. Plan ahead and make key control variables settings. Don’t forget to add a maintenance mode setting.
- 8. 4. Architect for flexibility Separate data and application logic into separate contracts. You can upgrade app contracts with no adverse impact.
- 9. 5. Create access controls Don’t hard code permissions. Use white lists in which you can register/deregister authorized callers.
- 10. 6. Use SafeMath Don’t gamble with large number arithmetic. Use the SafeMath library.
- 11. 7. Fail early (a.k.a. reduce gas cost) Use require(…) at start of function for prerequisites and minimize cost.
- 12. 8. Fire meaningful events Strategically fired events with indexed parameters can benefit from ultra-cheap log storage and increase flexibility for calling applications.
- 13. 9. Don’t use loops Block gas limits make loops dangerous as longer loops may never finish. Have the calling app handle the iteration.
- 14. 10. Customize ERC20 Use shadow variables to finesse ERC20 interface functions. Example: transfer() can block based on shadow escrow variable.