Author

Topic: So how do you go about doing your own DD on ICOs? (Read 75 times)

full member
Activity: 854
Merit: 100
Thanks for your post, it consist of most useful information. I would add also market research - see of the project has its competitors and why it is better.

member
Activity: 98
Merit: 12
 I hope we can share and learn from one another so we get better at avoiding scammy and lousy ICOs, and finding the gems.
----------------------------------------------------------------------
How I go about doing DD:
1. Read the whitepaper (of course!). I make sure that I get a rough understanding of what they are trying to do, most importantly making sure their project solves a real world problem. I question their proposal, if it is something that needs a blockchain.

2. Team composition - a project with good tech but without someone good in business is no-go for me.

3. Skillset - Things I look at when I am on the team's LinkedIn (is it a newly created account? What is their history, and most importantly how many people acknowledged their listed skillsets?) What about the member in charge of business? What are his record in managing businesses like?

4. Achievements/patents - I will Google as much as I can about their achievements if any. It will be very nice if the team already has patents.

5. Shillings - I look out for potential paid shills. Shill posts on Reddit (by newly created accounts). I tend to avoid new projects shilled by Suppoman because I know he's paid to shill.

6. Communication - How is their telegram channel being moderated? Do they ban people who asks questions? Are they actively responding to questions about their projects?

7. Words used - When a project has words like "moon" on their website or roadmap, then it is definite no-go. It is just trying to get moonbois on board.

8. Hardcap - projects with very high hardcap (30 million is my threshold) is a red flag to me. Potential cash grab.
--------------------------------------------------------------------------

What about you guys? Smiley
Jump to: