/ico-check

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Token Desk - Due diligence #2

Closed
hterrence opened this Issue Oct 24, 2017 · 1 comment

Comments

Assignees
No one assigned
Labels
Added to icocheck.io Due diligence Multiple red flags Non-transparent Past ICO Warning!
Projects
None yet
Milestone
No milestone
2 participants
@hterrence @icochecker
@hterrence
Collaborator

hterrence commented Oct 24, 2017

Company's website: https://www.tokendesk.io
@icochecker

This comment has been minimized.

Sign in to view
Collaborator

icochecker commented Nov 15, 2017 •
edited

TokenDesk (TDS)

Team

Tomas Mickauskas - Tokendesk advisor was involved in a charity scam.

Source:

Overview of the charity scam and multiple red flags:

Company

Tokendesk LTD
3rd Floor 207 Regent Street
London W1B 3HH
England

Incorporated on: 27 September 2017

Director:

Addtional info

Github

Product

Smart contract

  • Contract on Github
  • Contract not deployed at start of crowdsale.
  • Contract still not deployed as of 15 November 2017.

Vesting

  • No vesting schedule

@icochecker icochecker added the Due diligence label Nov 17, 2017

@icochecker icochecker changed the title from Token Desk background check to Token Desk - Due diligence Nov 17, 2017

@icochecker icochecker added the Red flag label Nov 24, 2017

@icochecker icochecker added Vesting schedule < 2 years Multiple red flags Warning! Non-transparent and removed Vesting schedule < 2 years Red flag labels Jan 13, 2018

@icochecker icochecker closed this Jan 20, 2018

@icochecker icochecker added the Past ICO label Jan 26, 2018

@icochecker icochecker added the Added to icocheck.io label Feb 7, 2018

@sky2018hao sky2018hao referenced this issue May 5, 2018

Closed

Iagon - Due diligence #122

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment