First impressions-Kronos.io

[tbcoin]

It sucks, how can open this so? can not be called neither beta.

Nothing works, not a single link is working, problems with the certificate and not even work the basics done right.

I place 2BTC under my clear risk, to test I take a long position with 12BTC at 5.15678 with leverage 10.0:1.

Now I see that they sold all at market price 5.1937, with -12.33907 P / L , Leaving my account -10.33907BTC.

Long live the Bitcoinica!





Sorry for my bad English

[1713575367]

1713575367

[1713575367]

1713575367

[1713575367]

1713575367

[1713575367]

1713575367

[tbcoin]

I send a e-mail to support@kronos.io and although I have not been answered, I have recovered the 96.032% of my funds. 

Technical support very fast

[Matthew N. Wright]

I send a e-mail to support@kronos.io and although I have not been answered, I have recovered the 96.032% of my funds.  

Technical support very fast

Sorry about that. We are in the BETA stage at the moment and the engine will restart sometimes during this beta testing process.

Your funds were recovered because we noticed your wrongly closed positions and restored them for you.

Look forward to more beta testing and thank you for taking it for a spin!

[tbcoin]

I send a e-mail to support@kronos.io and although I have not been answered, I have recovered the 96.032% of my funds.  

Technical support very fast

Sorry about that. We are in the BETA stage at the moment and the engine will restart sometimes during this beta testing process.

Your funds were recovered because we noticed your wrongly closed positions and restored them for you.

Look forward to more beta testing and thank you for taking it for a spin!

Thanks.
Sorry for first post in hot 

I sent another email, because now I have trouble withdrawing funds.Although I have no intention to withdraw, I would like to continue testing your platform, if I do't say, does not fix 

[Matthew N. Wright]

I send a e-mail to support@kronos.io and although I have not been answered, I have recovered the 96.032% of my funds.  

Technical support very fast

Sorry about that. We are in the BETA stage at the moment and the engine will restart sometimes during this beta testing process.

Your funds were recovered because we noticed your wrongly closed positions and restored them for you.

Look forward to more beta testing and thank you for taking it for a spin!

Thanks.
Sorry for first post in hot 

I sent another email, because now I have trouble withdrawing funds.Although I have no intention to withdraw, I would like to continue testing your platform, if I do't say, does not fix 

No worries! The site is not yet complete and that's why we're closing all positions at a 0 loss. Have fun with it and thank you again for your contribution to the testing phase!

[weex]

I can't stress enough the need for testing with bots that do random things. I didn't check if you have an API but this is the #1 reason to write one from the beginning.

[caston]

Are you planning to allow margin trading of alt coins?

[tbcoin]

WTF?

This is a failure, an error, a scam or a hack?

This this is the status of my account, I remind you that I deposited 2BTC, what is missing is due to failure of the platform.




By going to refresh it I get this message and will not let me login.

[caston]

That's sounds pretty serious man. Better do what he says!

[tbcoin]

I've already sent an email asking for this...

[Matthew N. Wright]

I sincerely hope this is either a joke, a trol or a misunderstanding but as I've been away on business for almost a week I haven't been keeping track of Kronos as much as I woukd have liked to.

I hate to say this but OP was never authorized to have an invite code and it seems someone thought it was in their best interest to pass them out like candy without giving any disclaimer as to the pre-beta nature of the accounts that would be signed up.

I assure you that your funds are not lost and I think one of the backend developers misunderstood the situation. I'll try to track down the specific issue. Until then, OP please stop using the account as the entire system is pre-beta and it is obvious you do not understand that having started this thread in the first place.

To everyone else, do your job right and stop leaking invited codes to people who don't know what 'pre-beta' and 'testing' mean

EDIT: As it turns out, my suspicions were correct. One of the developers misunderstood the pre-beta situation and one of our invited testers was trying to test the security of the very insecure test server instead of just practicing to use the trading tools. Ignore the "warning" as I'm sure it was meant tongue-in-cheek. We'll reset the test server and correct the issue. If ever (now or in the future) you experience any difficulties using the trading platform or during testing you happen to have funds suddenly vanish during a reset, just email support@kronos.io and we'llget things resolved for you. Cheers!

[tbcoin]

I know that this in testing.
In the OP I said clearly that I opened because it seems that the performance was way too poor to allow in anyone, even pre-beta, although it is obviously the opinion of an inexperienced

Then I started to like your platform, the new look is also very attractive and have continued doing tests without problems.

I signed up as soon as I learn of the existence of kronos.io and so I think I arrived an invitation when opened, no one has passed. the May 23 I receive a welcome mail:
"
Your account is successfully created, however you must activate it
You can do so by clicking the link below:
Activate Now
....
"

EDIT:

Already answered, thanks;). I hope my account will be unlocked soon, as I would like to continue testing the platform

regards

[terrytibbs]

By going to refresh it I get this message and will not let me login.

Looks like an amateur XSS exploit. Don't do what it says. Actually, don't use the site at all until you get confirmation that it's been fixed.

[tbcoin]

By going to refresh it I get this message and will not let me login.

Looks like an amateur XSS exploit. Don't do what it says. Actually, don't use the site at all until you get confirmation that it's been fixed.

...

EDIT: As it turns out, my suspicions were correct. One of the developers misunderstood the pre-beta situation and one of our invited testers was trying to test the security of the very insecure test server instead of just practicing to use the trading tools. Ignore the "warning" as I'm sure it was meant tongue-in-cheek. We'll reset the test server and correct the issue. If ever (now or in the future) you experience any difficulties using the trading platform or during testing you happen to have funds suddenly vanish during a reset, just email support@kronos.io and we'llget things resolved for you. Cheers!

[terrytibbs]

Oh, sorry about that, not sure how I missed it.

[nox_pp]

And the security certificate is bunk. With Firefox:

Code:

kronos.io uses an invalid security certificate.

The certificate is not trusted because no issuer chain was provided.

[swissmate]

wow, what a bad code it has.

[davout]

And the security certificate is bunk. With Firefox:

Code:

kronos.io uses an invalid security certificate.

The certificate is not trusted because no issuer chain was provided.

That's actually a pretty common problem that doesn't denote a flaw, the certificate is probably valid.
It's mostly just Firefox being picky.

[Foxpup]

And the security certificate is bunk. With Firefox:

Code:

kronos.io uses an invalid security certificate.

The certificate is not trusted because no issuer chain was provided.

No idea why you would be seeing that. It's got a perfectly good issuer chain: kronos.io -> PositiveSSL CA 2 (COMODO CA Limited) -> CA Root. Are we both looking at the same certificate (SHA1: 0aa96a3a3ab2accaceb3d77847174b1427de6a37; MD5: 22c32d8cbe8eb27cf8f9e65e457deb48)?

[terrytibbs]

No idea why you would be seeing that. It's got a perfectly good issuer chain: kronos.io -> PositiveSSL CA 2 (COMODO CA Limited) -> CA Root. Are we both looking at the same certificate (SHA1: 0aa96a3a3ab2accaceb3d77847174b1427de6a37; MD5: 22c32d8cbe8eb27cf8f9e65e457deb48)?

Works for me. Same cert.