smart contracts best practices

This page demonstrates a number of patterns which should generally be followed when writing smart contracts. The following recommendations apply to the development of any contract system on Ethereum. Calls to untrusted contracts can introduce several unexpected risks or errors. External calls may execute malicious code in that contract or any other contract that it depends upon.

Educational Deployed on Ethereum Mainnet solc-js - JavaScript bindings for the Solidity compiler. solidity-parser - Solidity parser built in JavaScript. sulk - Configurable contract compilation. ocaml-solidity - OCaml library providing a parser, a typechecker and miscellaneous utilities for manipulating contracts. 👉 For a comprehensive list, see results for "Solidity" on Visual Studio Marketplace.

 This document provides a baseline knowledge of security considerations for intermediate Solidity programmers. It is maintained by ConsenSys Diligence, with contributions from our friends in the broader Ethereum community. Our amazing community has also provided translations in Chinese and Vietnamese.

While it is usually quite easy to build software that works as expected, it is much harder to check that nobody can use it in a way that was not anticipated. In Solidity, this is even more important because you can use smart contracts to handle tokens or, possibly, even more valuable things.

Visit the documentation site: https://consensys.github.io/smart-contract-best-practices/ Read the docs in Chinese: https://github.com/ConsenSys/smart-contract-best-practices/blob/master/README-zh.md Read the docs in Vietnamese: https://github.com/ConsenSys/smart-contract-best-practices/blob/master/README-vi.md Feel free to submit a pull request, with anything from small fixes, to full new sections. If you are writing new content, please reference the contributing page for guidance on style.

The following is a list of known attacks which you should be aware of, and defend against when writing smart contracts. One of the major dangers of calling external contracts is that they can take over the control flow, and make changes to your data that the calling function wasn't expecting.