Please note that we are working on finishing the whitepaper, this is normal with many ICOs. There is only subscribing open at this moment, we will notify when the whitepaper is released, please have patience.
Please do not leave unfair derogatory comments as there is no crodwdfund started before we release the whitepaper. Please be responsible posters, do not spread FUD.
Please do not leave unfair derogatory comments as there is no crodwdfund started before we release the whitepaper. Please be responsible posters, do not spread FUD.
What?! Your Pre-ICO will be commencing this 28 Feb 2018 and until now you have no whitepaper. I don't buy your excuse that's normal with many ICOs... I guess what you're referring to are SCAM ICOs. I'll give you bits of advice from a certain developer, which I quoted below...
Quote
1. At the start of pre-ICO team should have a contract for automatic assets transfer, that contains a written set of rules for early investors – not on towel, not in the speaking form, but written in the smart-contract. Otherwise, collected assets can just fall in the pockets of founders, or they can change rules of the game in the middle of act – there are many examples.
2. The contract for pre-ICO should be a part of a bigger contract on ICO and do not be different tokens – it is unsafe form a standpoint of vulnerability and withdrawal of funds.
3. The contract for pre-ICO, and then on ICO should have a lower and upper barrier - if it does not – the team does not know what it wants - just a scam.
4. The contract for ICO should have escrow of the funds, received as a result of placement - it can be a frieze or multiSig with a voting condition. This will give you a guarantee against the expenditure of funds earlier than the team completed the previous stage.
5. The contract should have indisputable return of funds condition, in case of not reaching the lower limit of the collected pool. It is in the contract and not in the white book, if it is not – move on, it’s just a scum.
6. All contracts must be posted on GitHub, this will enable third-party developers to check the contract for the vulnerability, if the team has not taken care and before the ICO has not posted a bounty on the vulnerability.
7. The contract must specify the conditions for the team and for the bounty’s for vulnerability.
8. The contract must specify the conditions for not traded tokens - with clearly defined deadlines.
2. The contract for pre-ICO should be a part of a bigger contract on ICO and do not be different tokens – it is unsafe form a standpoint of vulnerability and withdrawal of funds.
3. The contract for pre-ICO, and then on ICO should have a lower and upper barrier - if it does not – the team does not know what it wants - just a scam.
4. The contract for ICO should have escrow of the funds, received as a result of placement - it can be a frieze or multiSig with a voting condition. This will give you a guarantee against the expenditure of funds earlier than the team completed the previous stage.
5. The contract should have indisputable return of funds condition, in case of not reaching the lower limit of the collected pool. It is in the contract and not in the white book, if it is not – move on, it’s just a scum.
6. All contracts must be posted on GitHub, this will enable third-party developers to check the contract for the vulnerability, if the team has not taken care and before the ICO has not posted a bounty on the vulnerability.
7. The contract must specify the conditions for the team and for the bounty’s for vulnerability.
8. The contract must specify the conditions for not traded tokens - with clearly defined deadlines.
Please take note of the highlighted words that the contract must be, "not on towel, not in the speaking form, but written in the smart-contract. Otherwise, collected assets can just fall in the pockets of founders, or they can change rules of the game in the middle of act – there are many examples."
