Introducing Events by trade[XYZ].
With Events, we’re advancing our vision of Hyperliquid as the universal exchange—a single, composable system for trading financial assets and real-world outcomes.
A user can deposit spot BTC, borrow USDC through portfolio margin, open a pre-ipo SpaceX perp position, hedge an upcoming SK Hynix earnings event with an events market, and pick the US Open winner—all from a single unified account on trade[XYZ].
Events will span sports, politics, economics, and financial markets, with an expanding range of categories and contract formats.
Our initial Up/Down markets cover equities, commodities, and pre-IPOs, powered by the depth and liquidity of trade[XYZ] perpetuals on HIP-3. These perpetuals provide continuous price discovery and serve as the resolution source, so each contract is grounded in XYZ's liquid market prices rather than an external oracle.
VSTDO retweeted
We are releasing the first liquid way to trade Anthropic.
For far too long, frontier assets have only been accessible to a select few. We are here to bring them to the masses.
Introducing EntropyIO. We’ve raised $14M led by Ribbit Capital and a $40M HYPE stake to build both improved and entirely new markets, the first of which are live on Hyperliquid today.
VSTDO retweeted
Clustering NVIDIA DGX Spark + M3 Ultra Mac Studio for 4x faster LLM inference.
DGX Spark: 128GB @ 273GB/s, 100 TFLOPS (fp16), $3,999
M3 Ultra: 256GB @ 819GB/s, 26 TFLOPS (fp16), $5,599
The DGX Spark has 3x less memory bandwidth than the M3 Ultra but 4x more FLOPS.
By running compute-bound prefill on the DGX Spark, memory-bound decode on the M3 Ultra, and streaming the KV cache over 10GbE, we are able to get the best of both hardware with massive speedups.
Short explanation in this thread & link to full blog post below.
VSTDO retweeted
Introducing Aviya - Institutional Credit on Hyperliquid.
Aviya is a private, compliance gated credit venue built on Hyperliquid, designed to extend structured credit access to institutional participants.
The platform facilitates bilateral, fixed-rate financing, initially against HYPE collateral, with a roadmap to expand into additional asset classes over time.
As capital allocators increasingly engage with on-chain markets, access to predictable, structured credit becomes a requirement. Aviya is designed to meet this demand by offering a more controlled alternative to fully permissionless lending systems, while still leveraging the efficiency and settlement advantages of Hyperliquid’s infrastructure.
We view Aviya as a core component in the development of HyperLend as the credit layer of the Hyperliquid ecosystem, enabling capital formation, leverage, and structured financing across both native and future tokenized assets such as equities, commodities, fixed-income instruments and even the likes tokenised pre-IPO companies.
Over time, Aviya will serve as a gateway for institutional credit into emerging on-chain markets, including real-world and tokenized financial assets.
We are also pleased to deepen our collaboration with @HyperionDeFi, working together on institutional business development and capital formation.
Aviya represents a continued step toward integrating credit natively into the broader Hyperliquid financial system.
gLend.
VSTDO retweeted
Major structural win for Hyperliquid.
A tier 1 CEX and the largest US-regulated stablecoin issuer are both staking HYPE and sharing revenue with the protocol. It's an admission that Hyperliquid is too dominant in perps to displace, so better to align and capture distribution.
We should see an increase of ~$140M+ in annualised revenue which will be used to buyback HYPE. This is the floor and will scale with USDC supply growth. Roughly a 20% increase in annualised revenue looking at recent data.
The USDC USDH fragmentation is now fixed.
Coinbase and Circle staking HYPE also reduces circulating supply.
Hyperliquid continues to get more attractive for institutions with Coinbase and Circle putting their weight behind the protocol.
Coinbase has announced its plan to activate AQAv2 on USDC as the treasury deployer, with Circle serving as the technical deployer responsible for CCTP and native cross-chain infrastructure. Both Coinbase and Circle have committed to stake HYPE to activate AQAv2. As part of this transition, Native Markets has agreed to terms granting Coinbase the right to purchase the USDH brand assets. With Coinbase, in its role as treasury deployer, sharing the vast majority of reserve yield revenue with the protocol, USDC will become the most aligned stablecoin on Hyperliquid. As a result, canonical outcome (HIP-4) markets will use USDC as the quote asset in a future network upgrade.
User and builder feedback has been consistent that fragmentation leads to degraded experience; now, the community no longer needs to choose between liquidity and protocol alignment.
The pioneering work of Native Markets in launching USDH as the first production-scale stablecoin sharing yield directly with a protocol in a purely onchain implementation made AQAv2 possible. The learnings and mechanics pioneered by USDH will live on in AQAv2.
The Hyper Foundation will give grants to eligible HIP-3 deployers, HIP-1 deployers, and builders who integrated USDH, supporting teams through migration over the next months. These grants reflect an ongoing commitment to teams who choose to build on Hyperliquid and align with the protocol. USDH markets are fully functional but will sunset over time. USDH remains fully backed, with feeless conversions to USDC and fiat available to users during this transition.
S&P Dow Jones Indices and trade[XYZ] have joined forces to launch the first official S&P 500 perpetual contract, available exclusively on Hyperliquid.
For 69 years, the S&P 500 has been a defining reference point for global finance. Until now, access to that benchmark has been shaped by market hours, intermediaries, and geography. Today, that changes.
The S&P 500 perp is now available 24/7/365, anchored by the official index data required for deep liquidity and institutional confidence at scale.
SPDJI helped define modern indexing. They are stewards of an iconic benchmark, the standard against which portfolios across the globe are measured. We are honored to bring that legacy on-chain.
Trade[XYZ] is bringing the world's most iconic assets towards a future of global, continuous markets — a future powered by Hyperliquid.
VSTDO retweeted
tetsuo still has me blocked and his team says that kind of bs..
alright then, i just looked at the repo that he published, and took the time to review the code again:
found 12+ critical security vulnerabilities. executable stack enabled via setjmp/longjmp with comments claiming "modern kernels enforce nx regardless". that's completely false. cmakelists.txt line 15-19 literally enables code injection vulnerabilities while telling users it's "safe"
arena allocator has textbook toctou race conditions (arena.c:117-134), integer overflows in allocation checks (156-166), missing bounds validation in aligned allocs (283-300). memory is never freed back to os in most paths, just accumulates until oom. "arena-based memory management" is broken
claims "complete dns resolver with dnssec".. grep -r "DNSSEC" returns nothing. no dnssec validation exists. dns has no source port randomization, vulnerable to cache poisoning. no rebinding protection, no rate limiting
compiler flags are INSANE: -wno-return-type, -wno-error=return-type, -fno-strict-aliasing, -wno-implicit-int. literally suppressing critical warnings to hide undefined behavior. no stack protector, no fortify source, no relro, no pie. basically zero security hardening
websocket mask keys use weak prng (socketws-frame.c:38), violates rfc 6455. http/2 has no hpack bomb protection, unbounded header decompression is classic dos. no stream id exhaustion handling, no flow control validation, priority tree manipulation unchecked
tls implementation skips ocsp stapling verification, missing hostname verification in multiple paths, no downgrade protection. ssl_secure_clear_buf gets optimized away by compiler. thread-local exception stack has zero synchronization, thats literal undefined behavior in c11
io_uring uses sqpoll without capability checks (socketpoll_uring.c:149), buffer registration has no bounds checking, submission queue overflow unhandled, multishot poll races everywhere
claims "zero dependencies except openssl" but requires liburing, zlib, brotli, pthread. claims "all custom. no libcurl. no libuv" while using multiple external libs
readme says "http/3 + quic (in progress)".. it's just string constants, no implementation. "simple api layer" mentioned but doesn't exist. "fuzz harnesses" claimed - zero fuzz files in repo. "examples folder (30+ demo programs)" but no examples directory exists. "unit/integration test suite" but no tests found
lack of input validation: no url validation, header injection vulns, integer overflows in size calcs, no bounds checking on user inputs. curl_main.c:249-260 header validation incomplete
this isn't "hand-rolled from scratch", it's false advertising. executable stack alone makes it unsuitable for any use. 8 critical vulns, 4 high severity, multiple memory corruption bugs, broken protocol implementations, and straight up lies about features
the readme claims "the code shown is battle-tested" while having zero tests. "passes full test suite" that doesn't exist. "fuzzed (not full coverage)" with no fuzz harnesses
i would also like to add that @tetsuoai and @dreamworks2050 claim that me and laurie were acting in bad faith with "unreleased code": the code was public when both of us posted the tweet. shortly after the gist got deleted along all the other tweets he posted arguing with us about this. don't twist the situation.
before you tell me to just submit issues and PRs instead of posting this: i took the time to make this review because i am sincerely upset and do not accept getting slandered like this for just criticizing false claims. i will not spend more time fixing a vibe-coded codebase that is falsely advertised. i don't care/mind that this is vibecoded, my problem is that this is falsely advertised to a following base of over 200k people who will not take their time to do their due dilligence like i did. i do not feel okay with you and your team claiming that i posted that code review "for engagement"
thank you, if you truly care about making this good then look at the issues i mentioned and fix them, if you're just doing this for engagement then so be it
finally, before you claim that you don't have me blocked, you keep blocking me and unblocking me, conveniently you blocked me again right after you released that repo, i wonder why
unavailable
VSTDO retweeted
of course, this code is complete AI slop.
Right off the bat, headers aren’t passed for POST/PUT/DELETE.
Both the help and -v options flat out lie about what was sent. Literally half of the flags are no-ops.
Oh, and it just silently drops authentication, so that’s fun.
But somehow your “99 fuzz harnesses” didn’t catch that.
This quoted post is unavailable.
VSTDO retweeted
We’ve been quietly building something new on Hyperliquid.
Here’s a first look at Hypercall - an on-chain options venue for every asset on Hyperliquid.
Over the past 6 months we've been busy building a best in class on-chain options experience
🔊 Sound on
VSTDO retweeted
TLDR: During recent volatility, Hyperliquid had 100% uptime with zero bad debt. This was Hyperliquid’s first cross-margin ADL in more than 2 years of operation. ADL does not change the outcome for any liquidated users. While some specific ADL providing trades were unfavorable, the aggregate effect of ADL was that traders realized significant pnl by closing positions at favorable prices that were only briefly available.
--
It’s sad to see some people attack Hyperliquid to deflect from their own platforms’ issues. Solvency and uptime are the two most important properties of a financial system. These are table stakes for any trading system, and gaslighting to convince users otherwise is unethical and irresponsible.
Below is more analysis on how Hyperliquid’s margining system handled the extreme volatility.
Background on liquidations
For a perps system to be solvent, every position must be backed by a minimum amount of collateral. This is called the “maintenance margin.” When positions do not meet the maintenance margin requirement, they are taken over by the system to be liquidated. Earlier today, many altcoins dropped by more than 50% in a short period of time. When this happens, long positions at 2x or higher leverage must be liquidated, or else the system accrues bad debt.
There were billions of dollars worth of positions liquidated on Hyperliquid in a matter of minutes. In a permissionless system, each user chooses their own position sizing and collateralization. Any system that does not liquidate the necessary users is irresponsibly gambling with other users’ funds. On Hyperliquid, every order, trade, and liquidation is transparently verifiable onchain. Many other venues significantly under-report liquidation data. This cannot be compared apples-to-apples against the fully onchain picture of Hyperliquid.
Background on HLP
HLP is a protocol vault with permissionless deposits that 1) provides order book liquidity and 2) performs backstop liquidations. The first role is negligible, with HLP trading less than 1% market share. The focus of this post is liquidations.
Liquidations are first attempted against the order book, and any user can provide liquidity to these market liquidations. Backstop liquidations occur when the order book does not have enough liquidity to absorb an undercollateralized position. In this case, HLP takes over the position along with its collateral. For improved risk management, HLP is split into several child vaults, and each liquidation is only sent to one child vault.
Background on ADL
Auto-deleveraging (ADL) is the liquidation mechanism of last resort, when market and backstop liquidations do not work. See Doug’s thread (link in reply) for a thorough explanation on the details of ADL.
Every ADL event has two sides: the “triggered” side is undercollateralized, while the “providing” side is decided as a function of profitability and leverage used.
Similar to backstop liquidations, even though providers to ADL are profitable on average, there are no guarantees for any specific event. Some ADL providing trades were unfavorable, such as when only some components of long/short portfolio were closed. The system is designed to minimize ADLs because they are unpredictable even if ADL providing trades are profitable on average. Because HLP is a non-toxic backstop liquidator, ADL is a rare settlement of last resort. As far as I know, this was the first cross-margin ADL event on Hyperliquid mainnet (ADL is more common for isolated-only assets such as hyperps, which are not backstop liquidated by HLP).
Summary of events
Over the course of 20 minutes, HLP backstop liquidated billions of dollars worth of positions.
HLP's philosophy has always been to provide liquidity of last resort. Contrary to misconceptions, HLP is a non-toxic liquidator that does not pick profitable liquidations. Instead HLP is a public good for maintaining system solvency. In particular, Hyperliquid has no liquidation fees. HLP’s design, including its multi-component child vault system, is the product of countless simulations, and allows HLP to maximally serve the benefit of the protocol while managing its own risk.
In fact, the liquidator child vaults of HLP themselves became undercollateralized in the course of backstop liquidating as many user positions as possible. This is by design, where child vaults are isolated from the other components of the overall strategy. HLP is treated no differently from other users when participating in ADL. In aggregate, HLP's child vaults were the largest addresses on the triggered side of ADL by more than an order of magnitude. The addresses on the providing side of ADL against HLP’s child vaults realized hundreds of millions of dollars in additional profit relative to the prices shortly before and after the dislocation.
On other venues, the liquidation engine is not transparent and therefore may not be subject to the same strict margin requirements as for normal users. On these venues, the exchange could have backstop liquidated more positions, bearing increased solvency risk to extract hundreds of millions in business revenue. This is not an acceptable tradeoff for Hyperliquid.
Finally, I know that this is a difficult time for many traders, and I hope the community can continue to support each other and grow together. As a contributor to Hyperliquid, I’ll continue to work my hardest to build the best possible platform that can house all of finance. Times like this highlight the importance of transparency and fairness in the financial system.
VSTDO retweeted
Day 168: $1k ->$100k Hyperliquid Eco Challenge
Portfolio value: $100,584.02 (+11.29%)
ONE HUNDRED THOUSAND UNITED STATES DOLLARS AND A NEW ALL TIME HIGH FOR THE PAPIFOLIO
Jeff tried everything to build Hyperliquid free of extractive mechanisms. But he didn't see papi coming. USDC straight from the orderbooks into the papifolio.
VSTDO retweeted
Instant reasoning is here: @Alibaba_Qwen 3-32B on Cerebras:
⚡ 1.2 sec reasoning latency
🚀 2,400+ tokens/sec
VSTDO retweeted
Introducing Qwen3!
We release and open-weight Qwen3, our latest large language models, including 2 MoE models and 6 dense models, ranging from 0.6B to 235B. Our flagship model, Qwen3-235B-A22B, achieves competitive results in benchmark evaluations of coding, math, general capabilities, etc., when compared to other top-tier models such as DeepSeek-R1, o1, o3-mini, Grok-3, and Gemini-2.5-Pro. Additionally, the small MoE model, Qwen3-30B-A3B, outcompetes QwQ-32B with 10 times of activated parameters, and even a tiny model like Qwen3-4B can rival the performance of Qwen2.5-72B-Instruct.
For more information, feel free to try them out in Qwen Chat Web (chat.qwen.ai) and APP and visit our GitHub, HF, ModelScope, etc.
Blog: qwenlm.github.io/blog/qwen3/
GitHub: github.com/QwenLM/Qwen3
Hugging Face: huggingface.co/collections/Q…
ModelScope: modelscope.cn/collections/Qw…
The post-trained models, such as Qwen3-30B-A3B, along with their pre-trained counterparts (e.g., Qwen3-30B-A3B-Base), are now available on platforms like Hugging Face, ModelScope, and Kaggle. For deployment, we recommend using frameworks like SGLang and vLLM. For local usage, tools such as Ollama, LMStudio, MLX, llama.cpp, and KTransformers are highly recommended. These options ensure that users can easily integrate Qwen3 into their workflows, whether in research, development, or production environments.
Hope you enjoy our new models!
VSTDO retweeted
>Ex-coinbase employees found Zora
>funded by Coinbase
>Dead for years
>Pivot to memecoin launchpad
>Get Jesse to shill non-stop for a week
>Launch useless token, keep 65%
Future of finance.
Base is for everyone.
Replying to @karbonbased
why does the token need to exist at all if it serves absolutely zero purpose?
this type of vapor for a project that raised $60M+ in total at a $600M valuation is just embarrassing for the space.
VSTDO retweeted
Summary of @chameleon_jeff's key points on Steady Lads:
- Markets still very active, traders not quiet til much later in a downturn
- % of Binance/Bybit volume are primary internal metrics, but don't tell the full story
- most people think they're just building an exchange, but it's a lot bigger than that & the perp DEX is just the 1st building block
- HLP was a very intentional decision early on to make market making more transparent & community-owned vs the landscape of Alameda & other insider strategies at the time
- Hyperliquid is much more decentralized than critics give it credit for, has had 16 validators (who you can talk to) since December
- Doesn't harbor ill will toward CEXes for listing JELLYJELLY on perps, says he wouldn't have done it personally "but business is business"
- Doesn't view Hyperliquid as a direct CEX competitor, think CEXes & DeFi should co-exist, & Hyperliquid is building how a significant portion of finance should operate on-chain, the original vision of DeFi
- Lots of misunderstandings around HyperEVM as a separate chain when it's really one & the same chain as the exchange (HyperCore)
- The purpose of HyperEVM is to make HyperCore programmable, because the most valuable things in finance don't already live on Hyperliquid
- Letting people build things themselves is the way to scale (especially aligned with the ethos of crypto), the exception is infra (including infra traditionally viewed as "apps")
- There's no other chain you can build on to access DeFi power users transacting billions of dollars a day, & fully integrated with a tier-1 exchange
- Tokenized equities, commodities, & forex will all exist on Hyperliquid & there's plenty of talent already building on Hyperliquid to do it
- Admits they've been entirely focused on building & poor at comms but that lets others shape your narratives for you
- There's so much to build, no point in fighting about drama or stupid takes on twitter
- Very short sighted to think in terms of price - in a post Bitcoin era, $HYPE's genesis distribution is as close as we've seen to Bitcoin but being "generous" to users has its cost (large airdrops with 0 cost basis)
- Long-term, if a large portion of finance moves onchain, there will be a lot more value accruing than exists in crypto today
- On memecoins: values freedom of expression
On stablecoins:
- the edge is in the real-world (banks, compliance, etc), but one of the strengths of HyperEVM is that it'll allow native stablecoins (including yield-bearing)
- Hyperliquid as a platform should be neutral in terms of which stablecoins can be used as collateral (& other features), but very opinionated as to how it makes that possible
VSTDO retweeted
2 takeaways from today's debacle;
1. $HYPE is not a consensus trade (entire timeline was grave dancing)
2. CEXes are truly terrified of Hyperliquid
🫡

































