The app gives users the full route through markets, veVXA, gauges, rewards, and portfolio state.
Architecture walkthrough
Read the protocol before you use the app.
Vertex Alpha is public on HyperEVM testnet. The app exposes swaps, liquidity, locking, voting, rewards, portfolio views, and points where marked live. This page separates live surfaces, standard infrastructure, Vertex specific logic, and the work required before mainnet.
01System map
Four layers, one reward loop.
The simplest way to read Vertex Alpha is as a fee routing product. Liquidity creates fees. Voting directs incentives. Lockers receive converted HYPE from real protocol revenue.
Tight range liquidity is used to make long-tail HyperEVM markets capital efficient from day one.
veVXA holders direct emissions and earn the majority fee share when markets generate revenue.
The product thesis is fee revenue converted to HYPE, streamed to lockers, with VXA used to bootstrap.
02What exists today
The public testnet is navigable today.
The current build gives users a complete route through the public testnet app. It is on-chain where marked live, and still clearly separate from an audited mainnet release.
Area
Current state
Status
Markets
Four HyperEVM testnet pools are connected through the app.
Live testnet
Locking
veVXA locking, voting, reward claiming, and portfolio views are wired into the public testnet app.
Live testnet
Vaults
Vault positioning and UI are roadmap-facing. The v2 vault product needs final contracts and risk work before mainnet.
Roadmap
Contracts
The current contracts are unaudited testnet deployments. Testnet tokens have no value.
Unaudited
03Build separation
Standard primitives vs Vertex IP.
A sharper frontend should not make every layer feel custom. Some pieces are familiar primitives. The Vertex value is how they are composed, governed, and monetized.
Standard primitives
Concentrated liquidity pools
Used to prove fee generation and capital efficiency for HyperEVM markets.
Voting escrow
Locks create governance weight and route incentives through gauges.
Gauges and rewards
Voting, emissions, and reward accounting can be understood as familiar DeFi infrastructure.
Vertex specific layer
Fee policy
The product is designed around real fees converted into HYPE for lockers.
Market selection
Initial focus stays on liquid-staking and yield-token pairs where liquidity can stick.
Vault roadmap
The future alpha layer needs its own contracts, risk model, first-loss logic, and audit trail.
04Reward flow
The protocol is easiest to understand as a loop.
The frontend should teach the product without a separate explainer deck. This flow is the core story the interface needs to make obvious.
InputUsers create market fees
Swaps and liquidity positions make revenue inside concentrated markets.
RouteVotes direct incentives
Lockers choose where emissions go, and fee flows follow productive markets.
OutputHYPE reaches lockers
The reward asset is HYPE, not emitted VXA, so the token is not the yield source.
05Product interface
Make the product easier to trust.
The public app should read like a protocol console, not a generic DeFi demo.
The interface should make contract status clear without asking users to read between the lines. Public testnet functions need visible labels, roadmap features need firm boundaries, and architecture context needs to explain why fees, locks, votes, and vaults belong in one liquidity system.
The design system should move toward an institutional product feel: precision, documentation, readable state, proof before persuasion, and no decorative motion that gets in the way of understanding.
Mainnet presentation rule
Vertex Alpha is not audited, mainnet ready, or value bearing until contracts, audits, launch approval, and risk disclosures are complete and published.