ClearHat (@xClearHat) header
ClearHat (@xClearHat) profile picture

NFT/Crypto Developers/Coders/Penetration Testers "Transparency is Key"

Joined February 2023
The lesson for most of us is this: Be careful and don't FOMO into something without research. For devs/marketers: Please consider that the regulatory arm of the govt is long and patient. There is no statute of limitations on securities crimes. Intent aggravates offenses. Judges/juries will likely be more lenient with objective accidents or unintentional software defects. Purposefully being misleading to cause others' harm will not win you any legal points and if you think you are outside meaningful legal jurisdiction, remember that there is a little thing called karma
1
1
175
Replying to @xClearHat
10/10 This is all about his intent and its looking that from the totality of the circumstances, that his intent was to commit fraud. A lot more will be revealed soon. Take a look at those few that made hundreds of thousands off the "intended exploit" for answers. More soon...
1
132
1/10 Many of you have been claiming that there was a flaw in @Pauly0x's #Pond0x contract, but he has stated that it is in there by actual design. xitter.cf/Pauly0x/status/1685073…
This Post is from a suspended account. Learn more
1
1
1
527
9/10 In summary: 1. @Pauly0x created a contract that he KNEW would make the Pond0x token worthless. 2. He knew the norm of token acquisition in the crypto industry. 3. He knew that posting the contract address, which was needed for anything, would induce worthless purchases.
1
1
102
10/10 This is all about his intent and its looking that from the totality of the circumstances, that his intent was to commit fraud. A lot more will be revealed soon. Take a look at those few that made hundreds of thousands off the "intended exploit" for answers. More soon...
1
1
195
So... @yugalabs HV-MTL game. Good news and bad news. The bad news is you can bot the living hell out of it. The good news, there's no purpose in doing so.
1
4
314
Geesh, @BoredApeYC ... when we said you should obfuscate, we did not mean obfuscate the visual effects so that non-botters have a tougher time than botters. The rules are still plain as day. 993-19359fd25878ad78.js changed to 938-f7a10553e0db63da.js
1
11
1,028
We will be opening a discord and going over any flaws found in the reiteration of #DookeyDash that will be released tomorrow. Considering how @BoredApeYC easily got away with releasing a game that could effortlessly be botted, we are sure that hardly any changes were made.
2
9
801
The #1 #DookeyDash score, owned by Mongraal, may have beaten the validation system. Take a look at the 2:11 mark of the stream that Mongraal, himself, provided. (xitter.cf/Mongraal/status/162345…) We slowed it down... (1/11)
Ended 1st in dookeydash @BoredApeYC This is the last 3+ mins from my rank 1 score 🤝
52
35
8
125
95,638
The #1 #DookeyDash score, owned by Mongraal, may have beaten the validation system. Take a look at the 2:11 mark of the stream that Mongraal, himself, provided. (xitter.cf/Mongraal/status/162345…) We slowed it down... (1/11)
Ended 1st in dookeydash @BoredApeYC This is the last 3+ mins from my rank 1 score 🤝
52
35
8
125
95,638
Additionally, we maintain the assertion that it was possible to avoid ALL detection just by READING from the javascript file and using a bot to emulate mouse movements. (10/11) xitter.cf/xClearHat/status/16233…
Replying to @xClearHat
For the time spent on it, it actually performed very well. (23/43)
1
1
12
7,586
Unfortunately, @yugalabs / @BoredApeYC do not seem to be taking the issue of cheating seriously, as they write off the legitimate concerns outlined in this and previous threads as "fud." (11/11) xitter.cf/xClearHat/status/16238…
So, @yugalabs is deflecting from the controversy by declaring the client-side hacks as "commonly known," when they in fact rushed to try to obfuscate their code only 2 days before the close of the competition. (See below) xitter.cf/xClearHat/status/16233…
5
27
7,199