Post
Topic
Re: [ANN] [ICO] [WGR] | Wagerr | The Betting Blockchain | Bounties
by
Cryptadonis
on 30/06/2017, 20:57:39 UTC
Click to right arrow. It is 2 (two) stages on 26 june. Or I don't understand a problem?
Are you say about withdraw?

The original page, in my screenshot, did not have an "extra arrow" or blip for a second 26 June entry... There was just one until I pointed it out on here.

Why even have 2 blips for the same date anyways? That makes no sense... it was added afterwards.

This coin is sketchy and I'll be getting out as soon as a possibly can. Good luck to anyone else who's invested even more than have.

PM me I'll buy your coins.
Sure. Add me on Skype: CryptoAnna

Haha! Yeah! They can simply wait for a day or two to piss off their stakes at Waves if they have no faith in it.

But I don't think one who is able to sabotage his own ship does actually have any coins!  Grin

It's been four so far, with no updates from the team. Doesn't give much confidence and lacks any professionalism. I'd even accept an email where they apologize for not sticking to their first important deadline, and that they were working on it with an explanation on why they're behind. Are they going to manually be giving out tokens, going through each account separately? They have funds now, they should at least hire someone competent enough to handle distribution. Or even pay someone to keep us updated, for that matter.

Also, since no one seems to point out the following inconsistency: "The blockchain network starts", which is listed on the 26th... but their TestNet releases late Q4 2017. I mean what blockchain network? They don't even have one... and we don't even know if anything is even in development because their github is still empty. Again, red flags everywhere, but I'll let you guys make your own judgement from now on because I really don't care if you end up losing from this.


This is all we literally have on the code side of things:

 # HTML5-Wallet
-Wagerr HTML5 Wallet Develeopment
+Wagerr HTML5 Wallet Development

A 2 lined readme... which needed typo fixing.