3. A code issue:
• To fix or not to fix?
• Bug or vulnerability?
• Severity?
• Name?
Problem
Thus, we needed standardization!
#blockchainhackers, Prague, 29.10.2018
4. • no hierarchy
• no explanation
• items of different nature
• items of different frequency
Standardization
So, it’s not enough!
#blockchainhackers, Prague, 29.10.2018
5. o to work with:
• issues
• hacks
• tools rules
o to educate developers
o to improve audit experience
o to compare standardizations
What do we need?
So, we need classification!
#blockchainhackers, Prague, 29.10.2018
6. • classifies
• is self-explanatory
• gives high-level
understanding
Good classification
So we made our classification!
#blockchainhackers, Prague, 29.10.2018
14. Is it good?
classifies
is self-explanatory
gives high-level understanding
Help us!
• use it
• comment
• commit
github.com/smartdec/classification
#blockchainhackers, Prague, 29.10.2018