4 posts tagged with "Strategy"

Summary​

The clearest difference between HyperCore and Lyquor is not simply performance, EVM compatibility, or whether an application can be deployed around a trading system. The deeper difference is who gets to define the financial infrastructure.

HyperCore provides specialized financial infrastructure as part of the Hyperliquid system. Order books, matching, clearing, margin, liquidation, and core account state are built into the chain-level trading environment. Lyquor takes a different direction: it exposes the capability for developers and users to build specialized financial infrastructure themselves, as sequenced Lyquid network applications with shared state and runtime capabilities.

In short:

HyperCore provides specialized financial infrastructure.
Lyquor provides the capability to build specialized financial infrastructure.

Summary​

HyperCall is useful not only as an options venue case study, but also as a window into a broader Hyperliquid pattern. Hyperliquid is no longer just a high-performance perp exchange. With HyperCore, HyperEVM, and application-layer products such as HyperCall, it is moving toward a financial application platform: HyperCore is the specialized trading infrastructure, HyperEVM opens a programmable application surface around it, and specialized products can be built close to that financial state.

The important question for Lyquor is: if this class of business were built on Lyquor, what would become easier, more native, or more differentiated? The key distinction is that HyperCore is a purpose-built trading infrastructure, while Lyquor exposes the capability for developers to build specialized trading infrastructure as Lyquid network applications.

Summary​

HyperEVM is not just “EVM support for Hyperliquid.” A better way to understand it is as Hyperliquid's general-purpose application layer. HyperCore remains the high-performance financial core for order books, clearing, assets, vaults, staking, and other critical state. HyperEVM gives developers a familiar Ethereum-compatible surface for deploying contracts, composing applications, and connecting back to HyperCore.

That framing matters when comparing HyperEVM with Lyquor. The right comparison is not “which Lyquor VM equals HyperEVM?” The closer match is Lyquor's Lyquid network layer: the application-facing layer made up of Lyquid/WASM execution, on-chain sequencing, node-hosted runtime, network state, and Ethereum-compatible interfaces.

In one sentence:

HyperEVM runs the application layer as EVM contracts.
Lyquor runs the application layer as Lyquid network applications, exposed through Ethereum-compatible entry points.

这次 3 月 22 日的周会，讨论的内容比平时更发散一些，但回头看，其实主线很清楚。一条主线是技术上怎么把系统做得更稳定、更适合演示，也更接近可落地的交易基础设施；另一条主线则是，如果项目继续往前推进，应该以什么样的产品定位、公开方式和创业节奏去展开。

The March 22 weekly meeting covered a wider range of topics than usual, but the main direction became fairly clear in hindsight. One thread was technical: how to make the system more stable, more demo-ready, and closer to something that can serve as real trading infrastructure. The other thread was strategic: if the project keeps moving forward, what kind of product positioning, public-facing approach, and startup rhythm should support it.