AF has bought back and burned 44,661,178 HYPE tokens, worth approximately $2.19 billion.
HyperEVM gas fees + Trading fees have burned an additional 1,107,228 HYPE tokens.
Total: 44,661,178 + 1,107,228 = 45,768,406 HYPE tokens burned, valued at around $3 billion.
Every update continues to optimize and expand revenue sources, with all proceeds used to buy back and burn HYPE tokens permanently.
Total: 14.76% of the entire Genesis airdrop has been permanently burned.
Hyperliquid can’t just burn those tokens. Would a public company remove its ability to issue more shares in the future? Hyperliquid needs to retain the option to use those tokens if needed.
They can’t simply burn them now and then issue more tokens later.
As for the 38% allocated to future emissions / community rewards, this will most likely be distributed over a long period through staking rewards or another incentives campaign. The key point is: if this supply worth billions is ever used, it should be because it drives meaningful growth, adoption, and value creation — which would ultimately be shared with stakers, users, and HYPE holders. In that sense, it largely offsets itself. And if you want to factor those future emissions into valuation, then you should also factor in projected growth over the next 5 years. Otherwise, I don’t think it makes sense to use that 38% to compute market cap today.
For team supply, I agree it should be considered but to what extent? We now have historical data on team behavior: only 5% of the HYPE they were entitled to has been claimed. If you don’t want to account for that level of team exceptionalism / ethics, that’s your call, but we do have enough information to reasonably conclude that the full team allocation is unlikely to hit the market anytime soon.
Also, we already have billions worth of HYPE removed via the AF, millions of HYPE removed through HIP-3 deployers, DATs, unclaimed airdrop allocations, and eventually future HYPE buybacks from Hyperliquid.
If you want to look forward when accounting for emissions, then you should also look forward on the buyback / supply reduction side and remove what is realistically expected to come out of circulation.
But using FDV the way you’re doing here, without that context, is misleading to your readers.
The last time HYPE was $50:
- BTC was $125K
- ETH was $4600
- SOL was $235
- HIP-3 didn’t exist
- HIP-4 didn’t exist
- PURR wasn’t bidding HYPE
- HYPE ETFs didn’t exist
- Circle wasn’t giving HL 90% of their USDC yield
- People assumed team unlocks was 10M HYPE tokens monthly
NEW: hyperliquid:native IS UP OVER 90% THIS YEAR - OUTPERFORMING bitcoin:native, ethereum:native, solana:So11111111111111111111111111111111111111112, binancecoin:native, AND $COIN (@coinbase), WHICH ARE ALL DOWN DOUBLE DIGITS YTD
@androolloyd@HypurrFi Sad to hear this but understanding. You did everyone well always. Though it sucks about points given my heavy participation in hypurrfi, points are not promises. Best of luck in the future.
Hi guys, I know things have been a bit quiet here for some time, but I want to let you know that development has not stopped for a single day. The OmniAvatar loop is active and fully operational.
The next step is to fill it with games, content, players, and partners. During this time, I have been focused on AI-powered development, and I have successfully built an autonomous studio for creating trend-driven Roblox games, where OmniAvatar content will be integrated.
At this stage, I have been working behind the scenes, concentrating all of my attention on the product and the games. In the near future, I will step into the spotlight and start creating content around what I have already built and accomplished.
My current focus is on developing several game projects that will serve as the foundation of the Omni ecosystem.
@ultrayieldapp@hyperbeat Why don’t you tell our users you tried to hand over the vault to HyperBeat due to “Operational costs”
After we audited it, there was a 13 000 HYPE hole
And you didn’t tell us?
Either you lied, or demonstrated grave incompetence.
“Institutional” larpers
Hyperliquid
@Henrik_on_HL Yeah. Lost a bigger than I'd like to admit portion. Would've been wiser to buy spot with portfolio margin to maximize gains. Painful lessons
🚨 BREAKING: cPanel and WHM, the control panels behind an estimated 70+ million websites, have a critical security flaw that lets anyone become root admin without a password. CVE-2026-41940 affects every supported version. It’s already being exploited in the wild.
watchTowr Labs published the full attack today, after the hosting company KnownHost confirmed the bug was already being used to break into a significant chunk of the internet.
If you've never heard of cPanel: it's the dashboard that hosting providers and millions of website owners use to manage their servers, domains, email accounts, databases, and SSL certificates. WHM is the admin version that controls the entire server. If someone gets root access to WHM, they get the keys to the kingdom and to every apartment inside it.
How the attack works, in plain English:
🔴 Step 1: The attacker sends a deliberately wrong login. cPanel still creates a temporary "you tried to log in" record on disk and gives the attacker a cookie tied to it.
🔴 Step 2: The attacker tweaks the cookie to disable cPanel's password encryption. Normally cPanel encrypts the password field on disk. With one small change to the cookie, cPanel just stores it as plain text instead.
🔴 Step 3: The attacker sends a fake login attempt where the password field secretly contains hidden line breaks. cPanel does not strip these line breaks out, so they get written straight to the session file. Each line break creates a brand new fake record. The attacker uses this to inject lines that say "this user is root" and "this user already authenticated successfully."
🔴 Step 4: The attacker visits one more random page on the site to nudge cPanel into re-reading the file. cPanel then promotes the injected fake lines into its main session memory.
🔴 Step 5: On the next request, cPanel sees a flag that says "this user already passed the password check." cPanel trusts that flag, skips checking the actual password, and lets the attacker in as root.
From start to finish, the attack takes a handful of HTTP requests.
If you run cPanel or WHM, the patched versions are:
🔴 cPanel/WHM 110.0.x → 11.110.0.97
🔴 cPanel/WHM 118.0.x → 11.118.0.63
🔴 cPanel/WHM 126.0.x → 11.126.0.54
🔴 cPanel/WHM 132.0.x → 11.132.0.29
🔴 cPanel/WHM 134.0.x → 11.134.0.20
🔴 cPanel/WHM 136.0.x → 11.136.0.5
If your version is older than these, assume someone has already broken in and act accordingly. Patch right now, then rotate every password and key the server touched: root passwords, API tokens, SSL private keys, SSH keys, mail passwords, and database passwords.
Harden your shit. Might be too late already tbh. Like all the eco rugs over the years, "trustlessness" has started to mean more like it sounds to outsiders than what it actually means.