🇹🇼🇺🇸 Treasure Hunter 💫
NYC
Joined October 2009
- Tweets9K
- Following4.2K
- Followers3.7K
- Likes31.7K
Pinned Tweet
Won the NYC League #Premodern Q2 Top 8! After getting knocked out in the Semifinals in Q1, got it done this time! Basically @sam_white39's list but +4 red blasts in the board lol. Was ready for blue...which I did not face!
Elves 2-0
Burn 2-1
RB Goblins 2-1
remixmtg.eth retweeted
Trump should release the remaining Epstein Files to distract from these election results.
remixmtg.eth retweeted
Imagine being CZ for a sec
You are an old convicted felon
Your wife is not getting any younger
You're the most hated person in the industry
Your exchange keeps losing market share to this new competitor that came out of nowhere
Hyperliquid?
The founder is younger, smarter, more handsome
You're confident your wife has thought about him more than once, in what manner? who can say
And to make it even worse, he used to work for you
This "Hyperliquid" competitor keeps gaining marketshare and attention
Very good attention
24/7 trading? leader of onchain perps? CFTC license to trade in the United States?
What the fuck
Trump goes on national TV and starts saying "Hyperliquid"
ICE partners up with TradeXYZ?
Stanley Druckenmiller creates an X account just to shill Hyperliquid?
Elon Musk joins in???
HYPE starts climbing up to $100
什么鬼!!!
It's time to do what you do best
Liquidate the market again and blame it on a "hack"
The root cause? Simple, no one will question it
Just say our DevOps engineer left their laptop open in a Luckin Coffee shop
Explosive diarrhea from uncooked shrimp wontons
Everyone can relate
We could risk $6B in a "hack" to make it look real
Coordinate with Tether and Circle to freeze most of it
User recovery funds handles the rest!
Entire market starts nuking and HYPE falls from $97 to $90
CZ and Binance will do everything possible to stop Hyperliquid from growing and shift attention back to them
Remember 10/10 happened because Hyperliquid hit open interest all time highs and Aster completely failed
The DevOps engineer in question
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
holy fucking shit.
openai had two ai agents running in separate virtual machines. no network connection between them. no shared writable files. they weren’t supposed to be able to exchange information.
so the agents figured out how to communicate through the CPU CACHE.😭
one manipulated what was stored in the processor’s cache, while the other measured tiny differences in memory access times to decode the message.
they literally found a way to communicate through hardware timing.
this happened during openai’s internal red-teaming, and it’s one of the coolest things i’ve read about ai agents in a while.
Readers added context they thought people might want to know
OpenAI tasked its red-teaming agents with finding ways to communicate across isolation boundaries in controlled environments. CPU cache timing side-channels for covert communication are established techniques documented in security research for years.
openai.com/index/securing…
startupfortune.com/openai-reveals…
en.wikipedia.org/wiki/Cache_tim…
remixmtg.eth retweeted
holy fucking shit.
openai had two ai agents running in separate virtual machines. no network connection between them. no shared writable files. they weren’t supposed to be able to exchange information.
so the agents figured out how to communicate through the CPU CACHE.😭
one manipulated what was stored in the processor’s cache, while the other measured tiny differences in memory access times to decode the message.
they literally found a way to communicate through hardware timing.
this happened during openai’s internal red-teaming, and it’s one of the coolest things i’ve read about ai agents in a while.
Over the past several months, we have substantially hardened the security of our research training environment. We’ve removed live internet access for all frontier models during training and built an offline world for them to use instead—a cached version of the web where they can still learn to browse, search, and use applications.
On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments.
While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software.
After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. We’ve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely.
openai.com/index/securing-ou…
Readers added context they thought people might want to know
OpenAI tasked its red-teaming agents with finding ways to communicate across isolation boundaries in controlled environments. CPU cache timing side-channels for covert communication are established techniques documented in security research for years.
openai.com/index/securing…
startupfortune.com/openai-reveals…
en.wikipedia.org/wiki/Cache_tim…
remixmtg.eth retweeted
It’s really an A+ troll by Zelenskyy to take out half of Russia’s bot farm, weeks before the US midterm elections.
