Security best practices for dApps

My company Provide recently did a study with Emory University and Aprio to understand the patterns of blockchain adoption in business. 60% said the value of blockchain was in its security, yet the second largest barrier to entry was internal skills.

Our mission is to help developers become more productive. We built the Provide Platform to be a DevOps style platform to help, but there is still a lot of education needed. So, we partnered with Blockchain Ecosystem Advisors (BEA) to create a 101 style webinar series to review the principals, design patterns and tools to help deploy blockchain applications securely.

Smart Contract Best Practices—February 21, 12 PM EST
3% of smart contracts are not secure. This webinar will cover the top do’s and don’ts of building secure smart contracts on Ethereum and techniques to test security. Register now.

Access Sensitive Data via Blockchain Networks—March 7, 12 PM EST
Data privacy on blockchain flips the paradigm of data ownership where individuals permission their data to blockchain networks. This webinar explores how to build applications that consume external data and how to interact with sensitive data. Register now.

Smart Contract Design Patterns—March 21, 12 PM EST
Design patterns are generic, useful templates that are solutions to commonly occurring requirements. This webinar spotlights on some useful design patterns for smart contracts including contract self-destruction, factory contracts used to deploy child contracts, and name registry. Register now.

There is a blog post as well with some additional DevOps videos and explaining more about Provide and BEA.

If people get into the webinars, we will extend it with additional topics, and maybe even go up to a 201 level. So let's get the conversation going. What are some of your biggest security questions for developing your dApps?