Let be real. How many of you guys actually read the whitepaper? I read whitepaper sometimes, but reading multiple of them can be a burden and a headache. Do you guys got any tips on getting through whitepaper a little faster. It killing a lot of time. Thank.
Go to the sections: Token specifications, road map, team, use cases. That is to have some good idea of the project. Most white papers are just a display of words, but it is noticeable if the white paper is well thought.
And by the way never forget to read the disclaimer.
Let be real. How many of you guys actually read the whitepaper? I read whitepaper sometimes, but reading multiple of them can be a burden and a headache. Do you guys got any tips on getting through whitepaper a little faster. It killing a lot of time. Thank.
For a quick analysis of whitepaper, I chose several important parameters:1)Comprehensive information delivery
2)Readability
3)Clarity
4)Business plan presentation
5)Presentation of technical implementation
6)Technology
7)Decentralization
8)Developer Activity on github.
All parameters I estimate by 1-5 points. If there were more than 20+ points, then this project is not bad ...
But if you really want to invest in this project, then you need a full and detailed study.
Plagiarism and copyrights must be included.