Full Time Larper Hobbyist Rage Baiter Trader | Retard
Joined October 2024
- Tweets8.3K
- Following367
- Followers661
- Likes38.1K
hyperchan_dev retweeted
Sweet. It's a 1 megawatt nuclear microreactor that fits in a shipping container.
Gas-cooled, first by helium, then air.
Runs for five years, then you ship it back to the factory, where they take care of the spent fuel and refuel it.
hyperchan_dev retweeted
Tesla has Cybercabs with skeletons driving around Texas today
Elon won Halloween
hyperchan_dev retweeted
they really said
ICE and Trade[XYZ] plan to bring Hyperliquid-based perps to the U.S.
Subject to regulatory approvals, ICE will operate U.S. regulated versions of Trade[XYZ]’s markets, leveraging their expertise as the leading deployer of real-world-asset perps on Hyperliquid.
The new venue will operate separately to ICE’s institutional futures franchise and offer a trading experience designed for retail participation.
Once live, U.S. traders will be able to trade 24/7 across a range of assets spanning the macro complex including:
*Crypto
*Equities
*Indices
*Commodities
*Forex
Read more: spr.ly/6010BHq9X8
Users will access the platform through U.S.-regulated FCMs performing KYC/AML screening, including ICE's joint venture with OKX.
ICE and Trade[XYZ] will seek approvals to launch a new market built on Hyperliquid to operate KYC-compliant perp markets, including regulatory approvals to support leveraged trading.
hyperchan_dev retweeted
ICE and Trade[XYZ] plan to bring Hyperliquid-based perps to the U.S.
Subject to regulatory approvals, ICE will operate U.S. regulated versions of Trade[XYZ]’s markets, leveraging their expertise as the leading deployer of real-world-asset perps on Hyperliquid.
The new venue will operate separately to ICE’s institutional futures franchise and offer a trading experience designed for retail participation.
Once live, U.S. traders will be able to trade 24/7 across a range of assets spanning the macro complex including:
*Crypto
*Equities
*Indices
*Commodities
*Forex
Read more: spr.ly/6010BHq9X8
Users will access the platform through U.S.-regulated FCMs performing KYC/AML screening, including ICE's joint venture with OKX.
ICE and Trade[XYZ] will seek approvals to launch a new market built on Hyperliquid to operate KYC-compliant perp markets, including regulatory approvals to support leveraged trading.
hyperchan_dev retweeted
Binance hack could be another catalyst pushing more attention toward Hyperliquid
Whenever trust in CEXs gets shaken, traders start looking for alternatives. DEXs could benefit from that shift, but not every DEX is positioned to capture it.
The real winners will be platforms with proven security, deep liquidity, and strong user trust.
And @HyperliquidX is one of the strongest names in that category.
CEX uncertainty could be DEX opportunity. Hyperliquid is right in the spotlight.
hyperchan_dev retweeted
Binance's target withdrawal-enablement time is approximately 14 hours from now.
They said they would run their proof of reserves one hour ago.
No idea why it takes them 3 days to "prepare" their proof of reserves snapshot for release. Sus
At this point they should have already rebought all the lost tokens.
Let's see if they stick to their word.
hyperchan_dev retweeted
Tin foil hat time.
My theory is that Binance has had a hole in their balance sheet for a while now.
Today was their last-ditch effort to nuke crypto prices so they could buy back way lower, fill the hole, and maybe even make some money off the top.
They saw prices going up, realized the hole was going to get WAY bigger, and decided to nuke it.
Unfortunately for them, prices didn't drop nearly as much as they needed.
And I'm not buying this story about some random DevOps developer getting hacked and compromising the entire operation.
I've worked in enterprise software engineering. Nobody at companies of this size should have that kind of unilateral access.
Changes to critical infrastructure typically have to go through multiple layers of review. Engineering, security, DBAs, org leadership, etc.
In a properly secured Kubernetes environment, you aren't be able to just waltz into production pods and do whatever.
You're telling me one compromised DevOps engineer had enough access to cause BILLIONS in losses, and there wasn't a single additional control in place to stop it?
You expect me to believe that shit?
Something doesn't add up.
This is speculation, obviously.
hyperchan_dev retweeted
ICE DELETED THE TRADE[XYZ] TWEET
they probably just butterfingered it
accidentally invested
accidentally wrote a press release
accidentally spent half their earnings call explaining hyperliquid to wall street analysts
hyperchan_dev retweeted
Hype is deflationary
what do you think happens to the revenue when the whole world uses hyperliquid in the backend without knowing and all that revenue flows into buybacks of hype
hype is getting scarcer and scarcer every single day.. all you have to do is hold and wait and the price will go up in a long enough time frame
hyperchan_dev retweeted
Some people are panicking because @ICE_Markets partnership announcement with @tradexyz disappeared from X lol.
Come on bro. Just a couple of days ago, ICE's founder and CEO literally presented the partnership and strategic investment in tradeXYZ to investors during the earnings call.
It's not exactly something you can just delete.
hyperchan_dev retweeted
I find it strange if this was Lazarus because usually when they hack stuff, they launder it instantly.
This Binance hacker seemed ill-prepared for when they got the money withdrawn.
Funds were frozen onchain and they used an old wallet that minted Radbro Webring nft...
hyperchan_dev retweeted
I don't think it makes any sense at all to say that North Korea hacked Binance.
In the past, they had scripts set up to automatically start laundering stolen funds before they could be meaningfully frozen.
Now they're telling me that the hacker was manually clicking to dump shitcoins and accidentally burned a few million dollars doing so?
It just doesn't add up.
By far, the most likely scenario was that someone inside of Binance decided their compensation wasn't high enough.
Maybe it was the dev ops guy himself, but more likely someone he works with who had physical access to his machine for an extended period of time at some point.
Always open to new information against what I am saying.