gm

Hyperliquid is the most exciting team and product in crypto right now I've been a user of HL since early April and it's been a pleasure to use. Bridging in USDC on Arbitrum is seamless and there's plenty of liquidity, with good APIs for connectivity. In this post, I go into why I think the Hyperliquid team has what it takes to bring optimism back into crypto and improve the kind of applications we see in the future. > @chameleon_jeff and his team are long-term oriented Hearing Jeff talk about the vision and the team in: (1) youtu.be/HqCksxcX49w?si… (Flirting with Models, a podcast focused on quant strategies) (2) youtu.be/cxyUtPoC1-E?si… a more recent interview on 0xResearch It is the level of clarity with which Jeff talks about where Hyperliquid can go and the clever ground up design of the L1 to support protocol specific usages that makes Hyperliquid such an exciting product because the team building it knows the exact pain points of building similar platforms having a strong background in HFT trading and using other platforms previously. > A team with integrity The team is not here to grift its users and leave. They have accepted no VC capital and have been self-funded since inception. They could have taken a cut of the revenue generated in HLP, but they open-sourced it to users. The points program is purposely made opaque so that it is hard for airdrop farmers to come in for the sole purpose of inflating core protocol metrics. > Well-designed L1 with specific protocol primitives We've seen tons of applications pivot into developing their own chain and in most cases, there is little to no innovation other than the fact that they are building their own chain. Hyperliquid's L1 is designed from the ground up to facilitate the types of transactions that commonly occur on a perps dex protocol. For example, it is ingenious to bake the funding rates mechanism into the consensus layer of the protocol. The vault system comes about as the creation of a key-signing primitive to allow the creation of a new address and the ability to sign on behalf of it but not move funds from it. These sorts of engineering ergonomics are not simply afterthoughts but thoroughly thought out design decisions to be able to build a highly efficient L1. > Deep understanding of existing distributed systems literature/theory For HyperBFT, Jeff mentions in x.com/chameleon_jeff… that they implemented the HotStuff protocol by the wonderful @dahlia_malkhi and co, which is amongst the latest in modern consensus algorithms alongside Narwhal and Tusk, Bullshark, and Mysticeti from Mysten Labs. What's notable to me is that they understand that modern consensus algorithms are "fast enough" and the real problem lies in the execution layer. > Bottom-up approach with a lean team With a relatively small team comprising 5 engineers and a handful other members, Hyperliquid takes a bottom up approach towards building the product out. I think this strategy (akin to a greedy approach) is highly valuable because it leaves flexibility for the Hyperliquid L1 to explore around the edges to build the best infrastructure to house the future of finance. tl;dr: check out @HyperliquidX if you haven't today With how based @chameleon_jeff and the team are, I would not be surprised to see the team have a real fair launch for the platform's token and even for it to launch on the HL platform itself. Additionally, with no insiders (e.g. VCs), Hyperliquid could really be the neutral platform for the future of finance. I'm here for the ride, as are many others, see: - @crypto_adair : x.com/crypto_adair/s… - @mogie__ : x.com/mogie__/status… - @sershokunin : x.com/sershokunin/st… - @0xPasteke : x.com/0xPasteke/stat…

god I love hyperliquid

@Hypurr thank you jeff and team! Hyperliquid

thank you community hyperliquid

@zkTuring we're so back

HAPPY ALL TIME HYPE I’ve missed saying this

HYPE's security flaw is that it is the only number go up technology in crypto

ATHs

@chrisgrx_ @Sokio8D @InsilicoTrading when chris on insilico podcast?

Thank you for the gift @Sokio8D @InsilicoTrading 🤍 The cats seem to love the hoodie as well.

Take ur pnl of the last month. Annualize it over 30 years. Thars ur NW

Hyperliquid ETFs.

@timothymaarv this is nice!

AI flow for generating analytics… with sound 🤌🏾

@0xNairolf you should check out @trydocent_

people underrate how powerful it is to have every market in the same interface stocks commodities crypto prediction markets all one click away with the same wallet damn good

@DeepDishEnjoyer yume is goated

send noodz

@lex_node what was difficult about getting money out of one of these embedded wallet apps? haven't had a particularly bad experience so far

I really did not understand how big of an issue wallet UX is until running a crypto app. If (like me) you're a crypto OG / onchain maxi or you grew up at least using some DOS or something, you have a mental block against realizing that most people just do not know how to use a wallet--even for regular transactions, never-mind something complex like using a hardware wallet, bridging. or where you might need to switch between wallets for a single transaction flow, etc. It's deeply confusing to them in a way I don't think can really be fixed. At the same time, imo, most of the benefits of crypto are destroyed by "embedded wallets"--they are essentially custodial, and they also pose technical/UX puzzles of their own, just ones that surface later--i.e., when you have to get your money out of that specific app. Until this is solved, crypto app developers are stuck between a rock and a hard place--either preserve the fundamental self-sovereignty benefits of crypto and cap your adoption rather dramatically, or raise the question of why you are using crypto rails at all by making your app into a custodial fintech app that happens to use crypto.

I spent the past few days in Washington with @hyperliquidpc meeting with policymakers during the historic advancement of the Clarity Act. We discussed Hyperliquid, the benefits that it offers to American consumers, and the regulatory path to bring onchain derivatives markets into the United States. Some conversations were technical with an impressive baseline understanding of Hyperliquid. Discussions included how onchain trading is a financial innovation that has clear global user demand. Other conversations focused more on a first principles introduction to defi and the promise of onchain markets. It was encouraging to see bipartisan support for thoughtful regulation of crypto. I look forward to continuing discussions in DC and working hard to make American access to Hyperliquid a reality.

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

#features" target="_blank" rel="nofollow noopener">matte.app/#features any knows how this compares to screen studio?

@yenwod_ meaning a trader has to manually shuffle collateral around to trade different markets? how is this not a hidden implementation detail

Sharding a matching engine by symbol is fine, but what made Kalshi decide to ask traders to manually move collateral and route orders between shards? It's not obvious what problem this design would be a good solution for. Is there a regulatory consideration I'm missing?

Cerebras was a test. When SpaceX, Anthropic, OpenAI, and every other major company IPOs, the whole world will be watching Hyperliquid.

@lochieaxon @mbarvian this is sick

sometimes it's worth disabling animations when a user is dialling in a precise value using @mbarvian's <NumberFlow /> with a simple custom plugin can easily support this adaptive setup