These are basic recommendations that should be the foundation of securing your smart contract:
- The master git branch has the
require_recipientmethods available in the EOSIO library. They can be found in detail here and implemented here (they end up calling the methods implemented in the
- Understand how each of your contracts' actions is impacting the RAM, CPU, and NET consumption, and which account ends up paying for these resources.
- Have a solid and comprehensive development process that includes security considerations from day one of the product planning and development.
- Test your smart contracts with every update announced for the blockchain you have deployed to. To ease your work, automate the testing as much as possible so you can run them often, and improve them periodically.
- Conduct independent smart contract audits, at least two from different organizations.
- Host periodic bug bounties on your smart contracts and keep a continuous commitment to reward real security problems reported at any time.