Roadmap · sequence, not schedule

THE PROGRESSION.

ASHER is built in dependency order: the application layer and connected execution first, native market infrastructure later. The long-term objective is a progression from connected execution toward native ASHER markets and, beyond them, the ASHER Trading Network. The six phases below communicate sequence rather than fixed calendar dates — there are no dates on this page, and none implied.

The six phasesWhat is running today

The shape of it

Two rows, one direction

The data and intelligence layers do not change as the roadmap advances. What changes is where the order goes.

Today

  1. AsherCore
  2. AsherLabs
  3. Connected execution

Long term

  1. AsherCore
  2. AsherLabs
  3. Native ASHER execution
  4. The ASHER Trading Network

Part VIII · sections 41–47

The six phases

Phase 1 is where the ecosystem is today — AsherCore, AsherLabs, AsherSupport and connected execution through Hyperliquid are running. Phase 2 is partly underway. Phases 3 through 6 describe native ASHER infrastructure that has not been built: they set out the sequence and the architecture, and the status ledger on /transparency is the record of what is actually live.

  1. Phase 1Application layer

    Current phase

    Build the trader and creator ecosystem.

    Where the ecosystem is today.

    • AsherCore market-data infrastructure.
    • AsherLabs charting and trading environment.
    • AsherScript, indicators and strategies.
    • AI-assisted workflows, Copilot and Autopilot development.
    • Hyperliquid connected execution.
    • Creator publishing foundations.
    • AsherSupport integration.
    • Genesis preparation and security foundations.

    Readiness focusCoherent end-to-end trading workflows, stable product infrastructure, secure connected execution and a foundation for creator distribution.

  2. Phase 2Ecosystem & distribution

    Next

    Scale usage and the creator economy.

    Partly underway.

    • Creator onboarding and marketplace depth.
    • Strategy subscriptions and discovery.
    • Deeper automation workflows.
    • Expanded AsherCore APIs and data coverage.
    • Additional execution integrations where useful.
    • Developer tooling and ecosystem incentives.
    • Expansion of practical ASHER utility around product participation.

    Readiness focusMeaningful product usage, healthy creator supply, repeatable distribution and mature automation operations.

  3. Phase 3Exchange foundation

    Future

    Develop the core architecture for native execution.

    • Execution-engine research and architecture.
    • Market structure and order semantics.
    • Account, collateral and margin architecture where applicable.
    • Risk and liquidation architecture.
    • Native market-data pipeline.
    • APIs and WebSockets.
    • Liquidity and market-maker interfaces.
    • Security, monitoring and operational architecture.
    • Compliance and legal architecture appropriate to the selected market model.

    Readiness focusDeterministic execution, robust risk design, observability, security review and credible liquidity architecture.

  4. Phase 4Native test network / controlled markets

    Future

    Prove the execution layer under controlled conditions.

    • Testnet or controlled market environment.
    • Simulated and controlled trading.
    • Execution stress and failure testing.
    • Risk and liquidation testing where applicable.
    • Market-data validation.
    • API/WebSocket and market-maker testing.
    • Security review and bug-bounty preparation.
    • Economic simulations.
    • Direct AsherLabs and AsherCore integration.

    Readiness focusSystem behavior under load and failure, security evidence, market-quality testing and operational readiness.

  5. Phase 5Native ASHER markets

    Future

    Introduce native execution when readiness requirements are met.

    • Native execution integrated into AsherLabs.
    • Native market data distributed through AsherCore.
    • Creator and strategy connectivity to native markets.
    • Liquidity programs and market-maker connectivity.
    • Expanded ASHER protocol/economic utility where appropriate.
    • Continued interoperability with external venues.

    Readiness focusSecure launch, market quality, transparent operations and sustainable participant economics.

  6. Phase 6ASHER Trading Network

    Future

    Expand from native markets into a broader trading network.

    • Multiple markets and broader asset support where appropriate.
    • Deeper liquidity and professional market infrastructure.
    • Institutional and developer APIs.
    • Creator strategies integrated directly with native execution.
    • Protocol governance and ecosystem incentives.
    • Interoperability with external venues and networks.

    Long-term focusA programmable trading network connecting traders, creators, developers, liquidity and market infrastructure.

Current phaseNextFutureEach phase is labelled in words as well as colour. A phase marked Future is a direction, not a deployment.

Being precise

Not a closed ecosystem

Native markets are an addition, not a replacement.

Go deeper

The document, and the record

The roadmap above is Part VIII of the whitepaper, and the phase content on this page is read from the same source the whitepaper renders. For what is running right now — product by product, with its maturity stated — read the status ledger.

Read the whitepaperThe status ledger