Smart contract programming requires a different engineering mindset than you may be used to. The cost of failure can be high, and change can be difficult, making it in some ways more similar to hardware programming or financial services programming than web or mobile development. It is therefore not enough to defend against known vulnerabilities. Instead, you will need to learn a new philosophy of the development.

1. Blockchain Smart Contract
Best Practices
David Paluy
@dpaluy
September 2017

2. Prepare for Failure

3. Failure Preparation Checklist
Keep it Simple
Pausable Contract
Manage the amount limit
Define upgrade path
Stay up to date

4. Keep it Simple
Simple Logic
Clarity over Performance
Modularize code

5. Pausable Contract

6. Manage the Amount limit

7. Can I upgrade the Contract?

8. NO, but...

9. Upgrade path
1. Contract is eternal, unless destroyed
2. Make a workaround

10. Centralized?

11. DELEGATECALL
Read Solidity docs
a contract can dynamically load code from a different address at runtime...

13. Use latest stable libraries

14. Lock pragmas to specific compiler version

15. Explicitly mark visibility

16. References
Read the Manual
Solidity STD
Smart Contract Best Practices by ConsenSys

17. Safe and Secure Coding!
@dpaluy