Skip to content
This repository has been archived by the owner on Jul 5, 2024. It is now read-only.

HAT.Exchange formerly Hawala.Today - Due Diligence #136

Closed
ghost opened this issue Jun 30, 2018 · 18 comments
Closed

HAT.Exchange formerly Hawala.Today - Due Diligence #136

ghost opened this issue Jun 30, 2018 · 18 comments

Comments

@ghost
Copy link

ghost commented Jun 30, 2018

‼️ Update: Kucoin and IDEX delisted HAT token ‼️

No ICO but an airdrop instead.

telegram-chat

HAT.Exchange (formerly Hawala.Today, HAT)

Other Website

Bynary


  • Bynary, Inc. is supposedly the holding company of HAT.Exchange.

Team

Refused to provide any LinkedIn profiles for the "team" members instead preferring absurd excuses and non-answers:



Googling around, you can find some of them

Zeeshan Masood (CEO/CTO) | LinkedIn

From CorporationWiki:

LinkedIn profile in April left much to be desired:

It's recently been suspiciously spruced up with debatable info:


He claims to have been CEO of Bynary since March 2017 even though it didn't exist until March 2018 and also claims he was working for TekSystems at the same time he was supposedly working for Reach Communications Inc. as seen in the old profile. Both companies have been contacted to confirm links but are yet to respond.

As to the part that has been suspiciously left out of the revamped profile, he was the founder of ToggleWave, a company which was terminated by the authorities because of tax issues:

He and Navaid Yusuf were also involved in WorldTradeCorp as Treasurer and President respectively, yet another company that met its demise at the hands of the law:

Omer Masood (Board Director) | No proof that he exists ‼️

Navaid Yusuf (Board Director) | No LinkedIn ‼️

In addition to the failed WorldTradeCorp above, he was also the president of Micronix which is yet another company taken down by the law:

  • Sean Pettersen (Board Director) | LinkedIn
    This one went from knowing nothing about blockchain and being just another guy that works at TekSystems:


...to being the CIO of Bynary and having a "specialization" in blockchain within weeks despite the fact that there's nothing in his prior professional history to support that:




Mario Suwandy (Head of Design) | LinkedIn ‼️

This one claims to have been working for Bynary, Inc. since 2015 even though the company didn't exist until 3 months ago:


Advisors

Rhys Parry | LinkedIn - Does not mention Bynary, Inc. or HAT.Exchange

Recently, one of the HAT telegram members noticed that Rhys had taken up a job with a potentially competing project:

Rhys has updated his profile to reflect this new job at VLabs but there is still nothing about Bynary:


Even more interestingly, he's now been silently removed from the Bynary site:

Keep in mind that neither Rhys nor Yash below has ever confirmed any relationship with this project. Rhys has been contacted to confirm if he ever knew about his position on Bynary's site but is yet to respond.

Updated by admin August 6th 2018: In a youtube post dated 25th of July 2018 Rhys Parry confirmed that he was an advisor to HAT.EXCHANGE

Source: Youtube

Yash Rachakonda | LinkedIn profile - Does not mention Bynary, Inc. or HAT.Exchange

Curiously, most of the identifiable faces on this page are or were employees of TekSystems which is an IT staffing and services company.

Updated by admin August 6th 2018: In a linkedin post dated 6th of August 2018 Yash Rachakonda confirmed that he has been involved as an advisor to HAT.EXCHANGE

yash-rachakonda-confirms

I have been involved as an advisor on a very interesting product which will make crypto currencies accessible to virtually everyone.

Yash Rachakonda is using the past tense by saying that he has been involved as an advisor but is he still involved today?

PR / Marketing Advisor (Telegram display name: Edward IV) is anonymous - His identity is unknwon. ‼️

Company

Claimed to be a company since last year:



But actually incorporated, not their actual company, but a whole new holding company 3 months ago:

Bynary, Inc.

File Number: 6805550
Incorporation Date: 3 March 2018
Entity Kind: Corporation
Entity Type: General
Residency: Domestic
State: Delaware

Office Address: N/A

Registered Agent Information

Name: Cogency Global Inc.
Address: 850 New Burton Road Suite 201
City: Dover
County: Kent
State: DE 19904
Phone: 302-734-1450

Source: Delaware entity search

Smart contract

https://etherscan.io/address/0x9002d4485b7594e3e850f0a206713b305113f69e#code

Github

Closed source with no intention of open-sourcing:

Update: August 2nd 2018 - PR / Marketing Advisor (Telegram display name: Edward IV - Anonymous - His identity is unknwon) shared the Hat exchange github link

github

1 contributor adminhatexchange

3 repositories

SellerEscrow

sellerescrow

HAT.Exchange_Windows_Build

windows

https://github.com/adminhatexchange/HAT.Exchange_Android_Build

android

Product

Actual exchange yet to be released in any form. Various beta clients of a staking wallet is available for multiple platforms.

Vesting

They claimed tokens were locked under contract numerous times and even held a telegram poll to recalculate the then circulating supply based on that premise:


But that turned out to be a bold-faced lie admitted to by the team after this document (pdf) was released highlighting shady business going on behind the scenes. That forced them to seemingly become more "transparent" without actually being so.

No tokens were or are locked under contract, the vast majority of the supply currently sits in team-controlled wallets subject to their whims:




"bound to what we have stated in the whitepaper" while simultaneously admitting to breaking it (and of course calling the document that exposed it "FUD"). Impressive!

As if that wasn't bad enough, they continue to mislead naive token holders by claiming, in their new whitepaper, that tokens will be "unlocked" at some future time even though they were never locked in the first place:

Additional info

Lying About Token Distribution

Directly following their lie about locked tokens, they also lied about airdropping and paying bounties to the tune of 1M+ HAT tokens. Numerous times they claimed to have airdropped 1M HAT and extra for bounties:




But after that document came out, it turned out to be yet another bold-faced lie which they tried to excuse with silly accusations, handwaves and back-pedaling on earlier statements:

Clear contradiction pointed out when they attempted to rewrite history:

As should be clear by now, this project and its administrators/team have a penchant for back-pedaling on their earlier statements when trying to get out of a hard spot. This is just the beginning.

Lying About Applying for an MSB License

Prior to the release of the document and the events thereafter, they claimed they were anonymous because of their pending MSB License which was supposedly applied for in November, 2017:


You guessed it, that was yet another lie. They never applied for an MSB license, how could they? There was no company up until 2 months ago (which coincidentally was the 6th month since they supposedly applied)! While you can easily find the MSB applications of somewhat similar exchanges like Coinbase, Gemini, Robinhood and even the obscure CryptocurrencyMarket at FINCEN's MSB Registrant Search Database:




There is absolutely nothing for Bynary, Hawala.Today or Hat.Exchange:



Searching by state in Texas (where they were supposedly based) and Delaware (where the "holding" company, Bynary, was incorporated) instead of company name also comes up empty. If you're thinking it's not showing up because they've not yet been granted the license then see FINCEN's FAQ (pdf) that suggests otherwise:

The only reason there's nothing about Hawala.Today, Hat.Exchange or Bynary in FINCEN's MSB database is simple: they've not even bothered to file for an MSB license. They continue to mislead token holders and any request for information of said license and other info is met with pseudo-legalistic hand-waves, embarrassing vagueness, sidestepping of the question and even asking you to go through KYC (yes, you read that right) administered by a team whose identities are in question:






Tangent: Anyone who has followed this project long enough knows for a fact that the MSB was the de facto excuse as to why the devs were anonymous, for example:

Basically yet another attempt at rewriting history


If that's not enough, then their recent backpedaling on the MSB requirement in this newsletter should be enough:

The author of that newsletter would have us believe all references to an MSB license prior to this point were "unofficial", simply "sharing thinking" and misinterpreted as "set in stone" by the community. All the screenshots above show the disingenuity of such an embarrassing claim, it would take serious mental gymnastics to translate the above comments in the screenshots as anything but official or simply "sharing thinking". Here's more, by the second in command:






"need", "needed", "require", "waiting for", "like Coinbase [which has an MSB]"... if such comments are to be interpreted as "unofficial", "sharing thinking", "[not] set in stone", what on earth is official?

The next paragraph in the newsletter says:

But not too long ago it was:

Their whitepaper and comments in the telegram channel advertise a "wallet" to store and link your bank account/credit cards to. The previous whitepaper even going as far as promising insurance for those funds (that has of course been magicked away in the latest version):

If the "these funds do not belong to Hawala.Today" make you think "aha! It's different", realize that's exactly the same lingo Coinbase employs:

But there really is no shortage of complaints about Coinbase blocking people from accessing those funds they supposedly don't own, so much so that they're being sued. But at least they have an MSB license. Does the second in command offer any explanation as to why this 180 degree change occured? Perhaps an admission that they've never actually bothered to apply for an MSB? Nope:

From "we need the license [...] we're on schedule to get the MSB license" to "we dont need license for [fiat] now". I am sure the authorities are going to take very kindly with an MSB claiming it's not using vague arguments that don't particularly line up with reality.

Lying About Holding Trademarks to Hawala.Today & Hawala Token, and the Company's Location

That's what you would've been greeted with if you scrolled to the bottom of their previous and now offline hawala.today site. Of course it was yet another lie exposed in the document mentioned earlier. Right off the bat there is and was never any Hawala.Today company to which such trademark rights would've been granted. There's no trademarks for either of those brands in the USPTO database. This was, at least one version, of the excuse the second in command gave when asked about it:

Laced with three lies:

  • there was a Hawala.Today company as at February 13th, a lie as has been established above
  • said company was not in the US but actually in Estonia/Singapore/Switzerland, another lie
  • the trademarks are actually held there, yet another lie

There's no trademark for either hawala.today or hawala token in the Estonian database, general Swiss database, Singaporean database or the entirety of Europe for that matter.

Other Fumbles

  • Banning People For Pointing Out Blatant Contradictions

Then:


Now:


Tangent: There is not a single shred of evidence of a VC backing this company, not one. Following the document that was released (linked earlier), you can see the "funds" actually came from people buying their tokens on EtherDelta and IDEX


Pointing it out:

Banned:

  • Claiming to be fully compliant with all the laws

Then:

Now:

Their reason for the change? FINRA

This became particularly problematic when people had their tokens locked in their smart contract with no recourse for action while they were waiting for the beta staking wallet to be released which would then require KYC. Instructions to directly unlock them using the smart contract was discouraged by the team:





They effectively banned a user for trying to help one such individual out because it's apparently "illegal" to interact directly with their smart contracts:

Edited by admin on 26 Jul 2018: 3 private conversation screenshots of PR / Marketing Advisor (Telegram display name: Edward IV - Anonymous - His identity is unknwon) removed

A company that claims to be "globally" compliant makes the absurd claim that PII is not "valuable", processes people's very personal and valuable data without a DPO data and expects to retain the data indefinitely. Their second in command didn't even realize a name was PII:


The GDPR regulators will surely love that.

The "Advisor"

The "yawn" above is by the advisor, whether of Bynary, HATE or both going he can't seem to get straight. He also doesn't seem sure if he's on or off the team but as earlier screenshots show, he sure loves to attack people in public and especially in PMs:




Edited by admin on 26 Jul 2018: 5 private conversation screenshots of PR / Marketing Advisor (Telegram display name: Edward IV - Anonymous - His identity is unknwon) removed

Flags

Real Team: ➖ More proof needed to verify all team members. Core team member / founder must be director of the company. Omer Masood - No proof that he exists. Navaid Yusuf - No LinkedIn. PR / Marketing Advisor (Telegram display name: Edward IV) is anonymous - His identity is unknwon. ‼️
Github: ✅ Update August 2nd 2018 - PR / Marketing Advisor (Telegram display name: Edward IV - Anonymous - His identity is unknwon) shared the Hat exchange github link
Smart Contract:
Working Product: ➖ Staking wallet only, actual exchange yet to launch
Vesting: ❌ Lied about token lock and continue to mislead token holders
Have a Company: ❌ No team member is listed as the director of Bynary, Inc.
Transparent:

@stonesy88
Copy link

stonesy88 commented Jul 27, 2018

@CRYPTOCHECKR @icochecker Those screenshots are of my personal conversations, I gave permission for them to be posted pubically.

@hat-exchange
Copy link

@cryptochecker @icochecker @stonesy88

HAT.Exchange communicated with the page admin and admin agreed to remove private and personal communications w one of our team members. The private chats were conducted in confidence with the expectation of privacy, and we do not grant permission for them to be made public. Private chats do not necessarily reflect the views of HAT.Exchange.

We continue to stand by our public statements (including in the screenshots of our public chat) and will be clarifying why certain statements were made in the past, with a detailed explanation about how and why certain things changed.

@stonesy88
Copy link

You expect privacy? Given that your company has leaked my personal data on your Telegram and other Telegrams on at least 5 occasions? You have no clue how to conduct business, no understanding or respect of Data Protection laws in jurisdictions which your users reside.

@hat-exchange
Copy link

Yash Rachakonda confirms advisorship with HAT.Exchange. @icochecker: Please edit the post accordingly:

https://www.linkedin.com/feed/update/urn:li:activity:6432267187032981504/

@hat-exchange
Copy link

Rhys Parry was kind of enough to upload a video confirming his relationship with HAT.Exchange. @icochecker - please update and remove all false and inaccurate claims:

https://www.youtube.com/watch?v=IttjnLRVudU

@icochecker
Copy link
Collaborator

@hat-exchange

Regarding Rhys Parry the information was accurate at the time of posting.

I invite you to read the comment again:

Keep in mind that neither Rhys nor Yash below has ever confirmed any relationship with this project. Rhys has been contacted to confirm if he ever knew about his position on Bynary's site but is yet to respond.

@hat-exchange
Copy link

hat-exchange commented Aug 7, 2018

@icochecker - sorry, but they both just confirmed either an ongoing relationship (Yash) or a past relationship before moving on (Rhys). Yash’s LInkedIn now refers to Hat.Exchange, so the section of the review claiming he “does not mention the company” is now demonstrably inaccurate and proven to be false. We are expecting the false claim to be removed.

Secondly, Rhys was an early advisor but moved on to another project. He recorded a video confirming his earlier relationship with our company, which is the same as responding to the confirmation request the author of this review claims to have made. He confirmed the relationship. The claim made in the review is now shown to be false and we expect it to be removed.

Finally, if you’re going to use the weak argument that “the information was true at the time it was posted” to get around editing the post in the face of new and more accurate information, then HAT.Exchange can just as easily (and fully intends to) argue that the communications in regard to MSB licenses were “true at the time the posts were made” (because they were). The company began the MSB application process for 10 separate U.S. States, and then modified their business model so that MSB licenses would no longer be required by law. We have the documentation that the legal team began work on the MSB licenses for those 10 States.

ICO Check seems perfectly comfortable allowing damaging and untrue claims with no evidence whatsoever to remain. There is no evidence that the team “lied” about MSB licenses. The information was accurate at the time it was communicated.

@hat-exchange
Copy link

hat-exchange commented Aug 7, 2018

@icocheck - let it also be noted, for the record, that one of ICO Check’s Telegram admins banned me for unspecified reasons with no warning or opportunity to respond (I am the representative of HAT.Exchange tasked with responding to this issue). We plan to write our own review of ICO Check in an official statement to our large community, and ICO Check will deservedly be receiving a large red tag for “CENSORSHIP.”

@icochecker
Copy link
Collaborator

@hat-exchange PR / Marketing Advisor (Telegram display name: Edward IV - Anonymous) was banned for breaking the group chat rules.

@ghost
Copy link
Author

ghost commented Aug 7, 2018

@hat-exchange

sorry, but they both just confirmed either an ongoing relationship (Yash) or a past relationship before moving on (Rhys). Yash’s LInkedIn now refers to Hat.Exchange, so the section of the review claiming he “does not mention the company” is now demonstrably inaccurate and proven to be false. We are expecting the false claim to be removed

Clearly English is not your first language or you're so incredibly daft you don't realize the obvious contradiction in that comment. It was just confirmed, the comment is a demonstrable accurate piece of history.

Finally, if you’re going to use the weak argument that “the information was true at the time it was posted” to get around editing the post in the face of new and more accurate information, then HAT.Exchange can just as easily (and fully intends to) argue that the communications in regard to MSB licenses were “true at the time the posts were made” (because they were). The company began the MSB application process for 10 separate U.S. States, and then modified their business model so that MSB licenses would no longer be required by law. We have the documentation that the legal team began work on the MSB licenses for those 10 States.

Provide said documentation dating back to at least 27th November, 2017 ( the time the first claim about the MSB was made) and you'll be taken seriously. Until then this inane analogy holds no water.

ICO Check seems perfectly comfortable allowing damaging and untrue claims with no evidence whatsoever to remain. There is no evidence that the team “lied” about MSB licenses. The information was accurate at the time it was communicated.

Your inability to comprehend the English language and desperate grasping at straws does not make historical truths "untrue". It certainly doesn't make the demonstrable lies about your MSB license situation go away but hey, don't let reality stop you from grasping at said straws.

@hat-exchange
Copy link

@icochecker - Your Telegram chat admins are perfectly fine with allowing your members to post private information, such as bank accounts, phone numbers, and names and addresses, if the targets are members of the crypto project teams your group has decided to “bash.” Edward IV (anonymous and staying that way!) posted the public LinkedIn profile of the member of your group who has harassed, cyber stalked, trolled, and threatened our team members and their past employers for months. This individual posted his full name and home address right into your Public Telegram chat. No rules were broken. We’re done here.

@hat-exchange
Copy link

@CRYPTOCHECKR - we’re done responding and providing privileged information to this unprofessional, disreputable, hack of a project.

@ghost
Copy link
Author

ghost commented Aug 7, 2018

@hat-exchange

This individual posted his full name and home address right into your Public Telegram chat. No rules were broken. We’re done here.

After you posted it, amirite?

we’re done responding and providing privileged information to this unprofessional, disreputable, hack of a project.

Lol, no more pithy word salads as a "response"? Or have you run out of words to string together hoping the shear size of it despite the meaningless of the content will convince onlookers? You did get one thing right although presented as a projection - HAT is a demonstrably unprofessional, disreputable, hack of a project. Watching you guys try to get rid of the evidence of such unprofessional treatment of people by your "advisor" especially has been nothing short of amusing.

@icochecker
Copy link
Collaborator

icochecker commented Aug 7, 2018

@hat-exchange information that breaks the rules gets deleted. Let me remind you that you doxxed a user in the icocheck group by publicly revealing his identity. I invite you to read the group chat rules once again and kindly ask you to behave properly.

@ico-check ico-check locked as off-topic and limited conversation to collaborators Aug 7, 2018
@icochecker
Copy link
Collaborator

icochecker commented Aug 7, 2018

Yash Rachakonda confirms advisorship with HAT.Exchange. @icochecker: Please edit the post accordingly: https://www.linkedin.com/feed/update/urn:li:activity:6432267187032981504/

@hat-exchange Yash Rachakonda is using the past tense by saying that he has been involved as an advisor but is he still involved today? 🤔 Bynaryinc.com still lists him as an advisor.

I have been involved as an advisor

yash-rachakonda-confirms-label

@icochecker
Copy link
Collaborator

Issue is locked until further notice to prevent spam and off topic conversations.

@ico-check ico-check unlocked this conversation Oct 3, 2018
@alphonsoespinoza
Copy link

Here are the images OP deleted from the first post

**Images leaked on social networks and publicly available

They effectively banned a user for trying to help one such individual out because it's apparently "illegal" to interact directly with their smart contracts:

Edited by admin on 26 Jul 2018: 3 private conversation screenshots of PR / Marketing Advisor (Telegram display name: Edward IV - Anonymous - His identity is unknwon) removed

screenshot

screenshot

screenshot

#The "Advisor"

The "yawn" above is by the advisor, whether of Bynary, HATE or both going he can't seem to get straight. He also doesn't seem sure if he's on or off the team but as earlier screenshots show, he sure loves to attack people in public and especially in PMs:

Edited by admin on 26 Jul 2018: 5 private conversation screenshots of PR / Marketing Advisor (Telegram display name: Edward IV - Anonymous - His identity is unknwon) removed

screenshot

screenshot

screenshot

screenshot

screenshot

Source (publicly available information): https://telegra.ph/WARNING-HAT-EXCHANGE-LEAKED-10-03

⚠️ To report Hat-Exchange to the SEC:

https://www.sec.gov/tcr

@ico-check ico-check locked as off-topic and limited conversation to collaborators Oct 3, 2018
@icochecker
Copy link
Collaborator

icochecker commented Oct 3, 2018

Issue is locked until further notice to prevent spam and off topic conversations.
For additional info join the ICO Check Telegram group chat.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.