This article was published 3 years ago. Some details may no longer reflect current market conditions or recent developments.If you spot anything that needs an update, contact us.
Cover art/illustration via CryptoSlate. Image includes combined content which may include the use of AI tools.
This weekend in crypto saw several peculiar events unfolding, from a thought-provoking fake summit to prominent Twitter account hacks and discussions on potential technological advancements.
Uniswap fake event
In an extraordinary display of deception, a group in Shenzhen, China, staged an event under the guise of the “First Uniswap Asian Summit” and had a so-called “CEO of Uniswap” in attendance. However, as Hayden Adams, ‘inventor of the Uniswap Protocol,' stated on Twitter, the event was not associated with Uniswap or Uniswap Foundation and was likely a scam. The scammers even went as far as creating a fork of the Uniswap website, adding Chinese community content while linking to the legitimate Uniswap app.
Source: Twitter
Peter Schiff's fake $GOLD token
Peter Schiff, CEO of Euro Pacific Capital and renowned Bitcoin antagonist, had his Twitter account hacked, with the hacker promoting an alleged launch of a new cryptocurrency. The tweet encouraged followers to “Claim your $GOLD,” a fake crypto project linked to Schiff's favorite asset class. Schiff's son, Spencer Schiff, quickly alerted followers, urging them not to click the link and emphasizing that his father was likely hacked.
Pro-XRP lawyer, John Deaton, suffered a phone hack on June 4 amid a relentless cyberattack over several days. CryptoLaw, an account created by the attorney representing XRP token holders in the Ripple SEC lawsuit, responded to the hacker's tweet from the attorney's account.
Deaton took proactive measures to communicate with his Twitter followers, utilizing his daughter Jordan Deaton's Twitter account to notify people of the hack, stating, ” I still do not have access to my Twitter account. Twitter informed me that it could take 1-3 days.”
Source: Twitter
OpenAI fake $OPENAI token
In another surprising turn, Mira Murati, CTO of OpenAI, fell victim to a hacking incident aimed at promoting a fraudulent cryptocurrency. Trace Cohen, a serial entrepreneur, and investor, shared the news on Twitter, highlighting that AI and technology are only as strong as their weakest link, which often tends to be “a human” element.
The deleted tweet claimed the introduction of a groundbreaking token called “$OPENAI” driven by artificial intelligence-based language models. It encouraged users to visit a link to check their eligibility for an airdrop to their Ethereum addresses.
Elsewhere across Crypto Twitter, scams were less of a priority as Twitter Spaces in the crypto space continued to thrive. For example, Binance CEO Changpeng Zhao (CZ) held a Twitter Spaces AMA on May 31, where he discussed various topics, from Binance layoffs to potential support for the Lightning Network on Binance's platform.
CryptoSlate Daily Brief
Daily signals, zero noise.
Market-moving headlines and context delivered every morning in one tight read.
5-minute digest 100k+ readers
Free. No spam. Unsubscribe any time.
Whoops, looks like there was a problem. Please try again.
You’re subscribed. Welcome aboard.
A breakdown released on June 2 recorded that he acknowledged that implementing the Lightning Network would require significant adjustments to their secure wallet infrastructure. However, he expressed optimism about the possibility of the network being supported, especially for Binance Pay and different wallet services.
Another day, another scam
As the world of cryptocurrency continues to expand, the events unfolding this weekend on Crypto Twitter serve as a potent reminder of the challenges and risks accompanying rapid innovation. The cultural influence of Crypto Twitter is undeniable, fostering a community that thrives on knowledge sharing, spirited discussion, and real-time updates.
However, alongside the positive developments, the space has become a breeding ground for hackers and scammers seeking to exploit users' trust, leading to an increased demand for security and vigilance.
The multiple high-profile hacks over the weekend highlight the need for the broader industry to invest in addressing security concerns and ensuring the integrity of the ecosystem while maintaining the open discussion and collaboration that have come to define our industry.
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gid
ID used to identify users for 24 hours after last activity
24 hours
_ga_
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga
ID used to identify users
2 years
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utma
ID used to identify users and sessions
2 years after last activity
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Clarity is a web analytics service that tracks and reports website traffic.