Quote from: strongman8 on November 05, 2017, 05:58:31 PM

Would you like a DNA sample as well.

What does this coin do that separates it from the other 10,000 choices we have. Its a bit late in the game for another *** Ethereum coin.

We personally don't think we asking for much, but do understand the frustration been you have a newbie account. Anyway, our decision to utilize this format is to nurture real applicant with genuine interest in cryptocurrency. Our intention is not to collect BTCT ID and ETH addresses. We have a solid plan to build a platform that while earn a viable spot in this sphere, and in other to do that we need to make sure our applicants are not just random airdrop hunters but individuals with genuine interest in this emerging tech. With regards to EANT been just another ETH coin, the plan is to use the current ETH platform to jump start the idea, then take the necessary steps to encode and create the planned objective.

Quote from: malekbaba on November 05, 2017, 08:25:59 PM

May Be I made a mistake. I chose my user name in slack instead of member ID of slack, Is it a major mistake ? What to do now ? Now I know how to find out the ID. I want some one from the team to help me. I do not want to repeat the procedure , cause the system may find my new submission as fraud. Please OP help me. I do not want to waste the chance.
I followed all other formalities, provided all other info accurately

Our team are active slack users thus the mandatory slack requirement. But we took into account that most ppl are not versed on the slack platform. So we will remove the slack requirement. If you choose, you can still join the slack account, but it won't be mandatory. The telegram will still be in place to aid in curtailing devious applicants/ providing a forum for applicants to communicate, but the slack requirement will be removed.

Quote from: Memoransom on November 05, 2017, 09:31:13 PM

Your telegram group chat is unaccessible, just 200 members and is saying that the group is full

The team member that created the group, unintentionally forgot to make it a supergroup. The issue has been fixed.