Skip to main content

Deployed Surface and Launch Boundaries

Which Orvex features are planned versus deployed?​

The roadmap and contract directory answer this in two parts: the roadmap labels product phases as planned, while the address directory lists published contracts that still require explorer verification. A documentation page cannot by itself prove that a feature is enabled in production.

Orvex documentation describes architecture and intended product behavior. It does not by itself prove that a feature is deployed or enabled.

Published contract surface​

The current address directory lists token, governance, reward, routing, pool-management, and read-API contracts. Each address must be checked on the Robinhood Chain explorer for verified source, contract name, and current deployment state.

Planned product behavior​

The roadmap describes these capabilities as launch phases:

  • Swapping supported assets through classic and concentrated-liquidity pools.
  • Providing liquidity and managing positions.
  • Smart routing across supported pool types.
  • ORVX token launch, oORVX emissions, and veORVX governance.

The words “planned,” “upcoming,” and “full launch” mean that documentation describes intended behavior, not an availability guarantee.

What the documentation cannot establish​

Documentation alone cannot establish current TVL, active gauges, live APR, current fee rates, contract ownership, or whether a transaction will succeed. Use the verified contract, explorer events, and the live application for those questions.