Solidity: Documentation on best practices to not repeat the DAO hack
Look, everyone has been talking about this, and everybody has different ideas for solutions so that Solidity can grow as a language. However, in the meantime, it is imperative that developers know the best practices, what caused this bug to happen, and what absolutely NOT to do. If someone would like to take this documentation challenge on, I'd be more than happy to review your work.
VoR0220
All 7 comments
I feel like re-writing or re-working the Solidity documentation should be one of the top priorities for the Ethereum community. I'm tempted to take this on.
redsquirrel
on 20 Jun 2016
Bring it Dave :) I could really use the hand right now. I think we all could.
VoR0220
on 20 Jun 2016
OK, now I've done it. I've applied for a DevGrant to create "A Tour of Solidity" inspired by https://tour.golang.org. God help us.
redsquirrel
on 21 Jun 2016
I'm willing to help you out with that!
Denton-L
on 22 Jun 2016
@Denton-L make it happen ma man. I know how much time you spend in the docs and was waiting for you to jump on here.
VoR0220
on 22 Jun 2016
@Denton-L Awesome. Can you email me? dave.[email protected] Let's work on the DevGrant proposal together.
redsquirrel
on 22 Jun 2016
I think this has been properly handled now. Closing.
VoR0220
on 23 Jan 2017
Related issues
chriseth
路
3Comments
axic
路
3Comments
chriseth
路
3Comments
ddeclerck
路
3Comments
gitpusha
路
3Comments
Most helpful comment
OK, now I've done it. I've applied for a DevGrant to create "A Tour of Solidity" inspired by https://tour.golang.org. God help us.