Topic: . - page 4. (Read 61280 times)
FREE DISTRIBUTION REPORT:
TODAY'S PAYMENT HAS BEEN SENT.
TODAY'S PAYMENT HAS BEEN SENT.
I still haven't received any free coins, after I registered last monday/tuesday...
Nice picture
I don't understand why people are complaining, I'm happy with everything, via free distribution, which is by the way very stable and I get my payment every day! For now I had 25 transactions.
In hindsight there are many red flags. Tbh I invested some BTC in this project, but if I look back that was a stupid decision.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
- Code is not published/auditable
- Only level 3 investors get the exchange code
- Virtually no information about the people behind the coin
- Ridiculous claims about 10000% profits are not unlikely. That alone of course is a big red flag.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
We are sorry about that, that's an early version of the code and we removed the md5() http://php.net/manual/en/function.md5.php function to encrypt passwords for debugging purposes. We will set up a git repository in a couple of days and give access to Level 3 investors with the newer version.
We always pay bounties for people finding bugs in our code, so we are open to this kind of findings.
Well then I deserve a bounty for that. I want it in BTC please. How much is my reward?
BTW: md5() is not a way to encrypt passwords, and if you only do md5() you will still be vulnerable because a rainbow table attack is possible. Md5-ing passwords is not sufficient.
Thanks, for the suggestion we will work on other way to encrypt the passwords to an stronger option, before the exchange is launched in release version.
Please send your Lithium address if you want a bounty for this.
Kind regards
md5() is not an encryption method, it is a hashing method with a pretty low entropy.
BTW I advise you to take my personal message seriously.
We will add another function.
I have already replied to you
In hindsight there are many red flags. Tbh I invested some BTC in this project, but if I look back that was a stupid decision.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
- Code is not published/auditable
- Only level 3 investors get the exchange code
- Virtually no information about the people behind the coin
- Ridiculous claims about 10000% profits are not unlikely. That alone of course is a big red flag.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
We are sorry about that, that's an early version of the code and we removed the md5() http://php.net/manual/en/function.md5.php function to encrypt passwords for debugging purposes. We will set up a git repository in a couple of days and give access to Level 3 investors with the newer version.
We always pay bounties for people finding bugs in our code, so we are open to this kind of findings.
Well then I deserve a bounty for that. I want it in BTC please. How much is my reward?
BTW: md5() is not a way to encrypt passwords, and if you only do md5() you will still be vulnerable because a rainbow table attack is possible. Md5-ing passwords is not sufficient.
Thanks, for the suggestion we will work on other way to encrypt the passwords to an stronger option, before the exchange is launched in release version.
Please send your Lithium address if you want a bounty for this.
Kind regards
md5() is not an encryption method, it is a hashing method with a pretty low entropy.
BTW I advise you to take my personal message seriously.
Sad to see that so many people fell for this scam. I knew after JimmyRecard's first post that something was wrong, since dev was dodging all the questions. Anyway good job Jimmy for busting this big scam!
What's the problem?
We are not associated in any way to http://bitsynq.com/
Our project is hosted in Namecheap servers so that's why the whois information shows Ross Technology
How about the BTC address? Also Nameserver?
Ignored, LOLZ! Continues to hype on gullible sheep.
In hindsight there are many red flags. Tbh I invested some BTC in this project, but if I look back that was a stupid decision.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
- Code is not published/auditable
- Only level 3 investors get the exchange code
- Virtually no information about the people behind the coin
- Ridiculous claims about 10000% profits are not unlikely. That alone of course is a big red flag.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
We are sorry about that, that's an early version of the code and we removed the md5() http://php.net/manual/en/function.md5.php function to encrypt passwords for debugging purposes. We will set up a git repository in a couple of days and give access to Level 3 investors with the newer version.
We always pay bounties for people finding bugs in our code, so we are open to this kind of findings.
Well then I deserve a bounty for that. I want it in BTC please. How much is my reward?
BTW: md5() is not a way to encrypt passwords, and if you only do md5() you will still be vulnerable because a rainbow table attack is possible. Md5-ing passwords is not sufficient.
Thanks, for the suggestion we will work on other way to encrypt the passwords to an stronger option, before the exchange is launched in release version.
Please send your Lithium address if you want a bounty for this.
Kind regards
In hindsight there are many red flags. Tbh I invested some BTC in this project, but if I look back that was a stupid decision.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
- Code is not published/auditable
- Only level 3 investors get the exchange code
- Virtually no information about the people behind the coin
- Ridiculous claims about 10000% profits are not unlikely. That alone of course is a big red flag.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
We are sorry about that, that's an early version of the code and we removed the md5() http://php.net/manual/en/function.md5.php function to encrypt passwords for debugging purposes. We will set up a git repository in a couple of days and give access to Level 3 investors with the newer version.
We always pay bounties for people finding bugs in our code, so we are open to this kind of findings.
Well then I deserve a bounty for that. I want it in BTC please. How much is my reward?
BTW: md5() is not a way to encrypt passwords, and if you only do md5() you will still be vulnerable because a rainbow table attack is possible. Md5-ing passwords is not sufficient.
We are not associated in any way to http://bitsynq.com/
Our project is hosted in Namecheap servers so that's why the whois information shows Ross Technology
How about the BTC address? Also Nameserver?
In hindsight there are many red flags. Tbh I invested some BTC in this project, but if I look back that was a stupid decision.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
- Code is not published/auditable
- Only level 3 investors get the exchange code
- Virtually no information about the people behind the coin
- Ridiculous claims about 10000% profits are not unlikely. That alone of course is a big red flag.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
We are sorry about that, that's an early version of the code and we removed the md5() http://php.net/manual/en/function.md5.php function to encrypt passwords for debugging purposes. We will set up a git repository in a couple of days and give access to Level 3 investors with the newer version.
We always pay bounties for people finding bugs in our code, so we are open to this kind of findings.
We are not associated in any way to http://bitsynq.com/
Our project is hosted in Namecheap servers so that's why the whois information shows Ross Technology
Please publish your source doe, so anyone can do an audit.
We are not associated in any way to http://bitsynq.com/
Our project is hosted in Namecheap servers so that's why the whois information shows Ross Technology
In hindsight there are many red flags. Tbh I invested some BTC in this project, but if I look back that was a stupid decision.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
- Code is not published/auditable
- Only level 3 investors get the exchange code
- Virtually no information about the people behind the coin
- Ridiculous claims about 10000% profits are not unlikely. That alone of course is a big red flag.
Of course, the same goes for your passwords at other parts of the site: the wallet, the ICO part, etc. You cannot be sure your information is safe.
Jump to: