Skip to main content
AlphaEngine has two related paths:
  1. the public beta Strategy Arena API path,
  2. the encrypted on-chain intent path for protected submissions.
They share the same evaluation principles, but they are not the same runtime surface.
Builders use the Strategy Arena API through api-router. The route surface is implemented and documented under API.

​
Public beta path

The public beta starts at api-router. The router owns public HTTP contracts, auth, request validation, and family dispatch. It does not own strategy math, simulation orchestration, AMM adjustment, ranking formulas, or operator runtime behavior.

​
Canonical backend sequence

Production PMF direction

data-pipeline -> simulation-service -> ranking-evaluation

Strategy logic

spot-strategies -> simulation-service

Execution adjustment

amm-math -> simulation-service

Public gateway

api-router -> public HTTP gateway
cofhe, listener-service, and alphaengine-contracts belong to the encrypted intent runtime, not the public beta API surface.

​
Encrypted intent path

This path is for protected strategy inputs and on-chain lifecycle records. AlphaEngineIntentController owns the contract events and state. The listener runtime polls lifecycle logs, decrypts permitted handles through the operator runtime, calls simulation-service, and records official evaluation results.

​
Ownership boundaries

​
Design rule

Public access is endpoint-driven through api-router. Internal packages remain implementation modules. Public docs should not present internal repos as the public SDK surface.

Private strategy evaluation flow

Follow protected inputs through the confidential evaluation path.

Strategy lifecycle

See submit, simulate, evaluate, score, evidence, and eligibility.

API overview

Inspect the public route boundary.

Repo map

Map modules to ownership boundaries.