Bitcoin Forum
May 25, 2024, 09:38:16 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Do you think Swace scamming their token holders?  (Read 95 times)
Jamjamz30 (OP)
Member
**
Offline Offline

Activity: 332
Merit: 12


View Profile
July 15, 2019, 06:40:34 AM
 #1

This is the first time I made a topic about one of the altcoins project here in the forum. Why I like to discuss this one? I want to know the view of the other members here in the forum regarding this things.

Swace started to promote their project since last year 2018 https://bitcointalk.org/index.php?topic=3675956.0 were their ico
will run up to July 15 2018. Now, since their project didn't reach at least the soft cap target, they oblige to ended it early. After a couple of months they've sent the bounty rewards to their bounty participants. Almost all of their bounty participants received it which was SWA to their on eth wallet , then they've waited for what would happen for the project until 2019 came in. Now just recently, since the team of swace found out and realized that IEO became popular, they've decided to ride with the trend. They've planned to launched Swace again but this time under by IEO rpogram, and here is their latest bounty https://bitcointalk.org/index.php?topic=3675646.0 were it will run until Dec. 22 2019 with different phase or tier. for the old SWA holders(BOUNTY PARTICIPANTS) of SWACE they must submit KYC for them to be eligible to swap their OLD SWA token to a new SWACE token. Now, I think there is something wrong with this rules the old SWA token was already in the wallet of their bounty participants. Meaning, if they fail for the KYC they won't illegible to swap it into a new token which is Swace, that's totally insane. In short, their SWA old token is useless, actually its no value at all. Then, I read their telegram channel where they took the blame for the bounty hunters who joined their bounty campaign of why their ICO of Swace last year failed, whoa! that's definitely wrong, As far as I can see, their bounty hunters did their part according to the rules they have, it is not their fault if the investors didn't come in to support their project or invest in it. Probably, their whitepaper and road map was not that attractive for the community investors by that time. Imagined, their project was running for almost 1 year. They are fooling their community about their project. But all of this was just my observation about it.
Have a good day..
Bttzed03
Legendary
*
Offline Offline

Activity: 2114
Merit: 1149


https://bitcoincleanup.com/


View Profile
July 15, 2019, 06:58:12 AM
 #2

Bounty hunters who joined in the previous campaign should be entitled to the new tokens without having to go thru KYC verification. They should not be covered with that rule since it was not part of the deal before.

I think a flag should also be created against Swace just like another campaign called Terragreen (see flag https://bitcointalk.org/index.php?action=trust;flag=454).
VanDeinsberg12
Hero Member
*****
Offline Offline

Activity: 1540
Merit: 507



View Profile
July 15, 2019, 07:55:56 AM
 #3

Bounty hunters who joined in the previous campaign should be entitled to the new tokens without having to go thru KYC verification. They should not be covered with that rule since it was not part of the deal before.

I think a flag should also be created against Swace just like another campaign called Terragreen (see flag https://bitcointalk.org/index.php?action=trust;flag=454).
OP, this guy was correct about that, all of the tokens that already distributed must be swapped automatically. But it looks like swace was trying to do something fishy.
What about investors who can't complete the KYC and they will definitely lost their token and that's a scam.

.......[url]CHOOSE LIFE      CHOOSE SPACE      CHOOSE FRIENDS...........[URL].....►  C O M I N G   S O O N.....
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!