Topic: Pros and cons of whitepapers - page 2. (Read 643 times)
Usually they all look like same to me as long as you dont go reading them upto their depth! The logics and protocol written in their can give good idea to technical person and for common investors like me, I just care about what is new in that paper and in what way it is different than the best once that I have already seen until now. So its more or less comparison for me but does give me idea about how to proceed with my investment. FYI : I read the whitepaper only if the project summary helps me understand what new in that. Dont fall for many of the project who just copy paste the dam thing!
Question for everyone, what are the signs of a good whitepaper and also signs of a bad one.
there is no benchmark to be a comparison in judging a white paper. most importantly, you should try to understand it especially for the concept issues raised into the white paper. if not logic, you can search other ico.
Good whitepaper should be brief and straight to the point. Albert Einstein said "If you cannot explain it in simple terms, you don't understand it well enough". Most whitepapers now a too long and full of irrelevant information. Good whitepaper should be problem, solution and how. Simple, no fancy words
good whitepaper should bring all the readers to learn something new, and not explain unimportant thing that generally we saw like others whitepaper
content of the whitepaper explain the point of the project, and at one page at least give a limit of word
i almost see the whitepaper like reading a whole dictionary
it will make people to skip or even didnt want to lazy read those whitepaper
content of the whitepaper explain the point of the project, and at one page at least give a limit of word
i almost see the whitepaper like reading a whole dictionary
it will make people to skip or even didnt want to lazy read those whitepaper
Question for everyone, what are the signs of a good whitepaper and also signs of a bad one.
A good Whitepaper should contain the following sections:- problem;
- suggested solution and product description;
- a description of the implementation of the token (like interacting with the product, Economics and technical implementation);
- team;
- token issuance and further plans.
At the same time, despite the fact that the section devoted to the project team is usually located at the end of the document, it is one of the most important elements.
And do not forget that Whitepaper is only a marketing tool, if the project is of no interest to anyone, even high-quality Whitepaper will not save it.
Apart from all the necessary dos and donts given above, Language is really important, written in easy to understand format, capturing interest with apt keywords and enough detail to get a clear picture. Typo errors are always a turnoff. Just keep it simple with team, project details, vision and solution highlighted.
A good white paper should have the following sections:
- A problem
- A proposed solution and the product description
- A description of the token commercialization (product interaction with economy and technical provisions of commercialization)
- Team members
- Tokens issue and perspectives
- A problem
- A proposed solution and the product description
- A description of the token commercialization (product interaction with economy and technical provisions of commercialization)
- Team members
- Tokens issue and perspectives
Yes, I guess a bad whitepaper can also touch all these questions but it will not open them up to the end. Here is a good video about whitepaper in general: https://www.youtube.com/watch?v=5ILpLo5TSnM
Good Whitepaper is well structured without exessive unnessesary information that clarifies the main question that appear from the side of investors. It has to have roadmap, analysis of the opponents, explanationa and expectation about the groeth of the token, the teammembers and information about them.
Personally, I argue a good whitepaper should include tokens statistics part. I think it is the one of the most important parts of a good whitepaper. What is total supply, price of token, soft cap? How many tokens go for crowd sale, for team, advisers and bounty.
The advantage is that it fully discloses its team, project prospects, and project planning. The downside is that for ordinary people to come to the book they can not tell whether the information they disclose is true or not. Many white papers have appeared. Liars are everywhere.
Question for everyone, what are the signs of a good whitepaper and also signs of a bad one.
A good white paper you can see the team behind them, this is the most important thing in it, what are their goals.
The drawback is that some con artists use a good white paper to blind investors' eyes.
The best white papers will be honest about why their solution needs the blockchain. Many projects freely admit that they’ll only be using the blockchain for token generation and some smart contracts management, and that’s perfectly okay. But if a startup claims to have some novel idea for blockchain-based carwashes or something like that, beware.
I argue that a good cryptocurrency white paper should explain how the technology will work, and the best white papers do so with varying levels of complexity and technical knowledge required.
A good whitepaper should indicate a specific plan. I generally like to see a detailed plan for the next 12–18 months (that includes a beta launch at minimum)
From my point of view, a good whitepaper should have the team section. I think it is the most important section of any whitepaper. I like to know who they are, what their objectives are, and what their reasonable solutions.
There are a few sections a good white paper must have:
- Problem
- Solution & Product
- Token Implementation (how the token works with the product, economics and technical)
- Token Deployment & Plan
- Team
- Problem
- Solution & Product
- Token Implementation (how the token works with the product, economics and technical)
- Token Deployment & Plan
- Team
I think that a good white paper should have a clear plan and a substantive role. It must be clear when it introduces its project, and it must be practical, and it must have sufficient innovation. This will attract a lot of investment. This will make this project better developed.
I think a perfect white paper won’t help a bad project. If the project team proposes a solution to a non-existent problem or to a non-essential problem, or if its members lack development experience and are not familiar with the blockchain, it’s highly probable that the project won’t be successful — even if its documentation is brilliant.
It’s vital that the white paper includes a detailed technical description of the project, and its future development plans (development roadmap). In theory, the team should present a detailed working plan for the next 12–18 months, which should include the beta-launch. If some tasks of the roadmap have already been performed, that may be considered as an advantage for the project team.
A good white paper should have the following sections:
- A problem
- A proposed solution and the product description
- A description of the token commercialization (product interaction with economy and technical provisions of commercialization)
- Team members
- Tokens issue and perspectives
- A problem
- A proposed solution and the product description
- A description of the token commercialization (product interaction with economy and technical provisions of commercialization)
- Team members
- Tokens issue and perspectives
Jump to: