QENOVRA.
M5 / PERMISSIONLESS SOLVER NETWORK

Compete to execute intent.

A QENOVRA Solver is an independent execution operator. It watches eligible intents, computes an execution plan, submits a bid, bonds value against correct behavior and — when selected — executes and settles the result through QSL.

Current status: M5.2 operator foundation is ready. Outside Solver operators now have a Public Testnet registration package, live SolverRegistry watcher, HTTP quote runtime, operator-signed on-chain bid bridge and winner-gated settlement tooling. The remaining acceptance gate is a fresh outside operator completing the full real Public Testnet flow. Open public enrollment is not enabled yet.
CURRENTM5.2 FOUNDATIONOperator package + chain bridge ready
NEXT GATEREAL OPERATOROutside Solver Public Testnet acceptance
ECONOMIC CONTROLBond + SlashAccountability by design
RUNTIMEQuote + ExecuteCapability-aware operator API

What a Solver will do

DISCOVER

Watch eligible intents

Read intents that fit the Solver's supported assets, venues, services and execution capabilities.

QUOTE

Compete on execution

Calculate a route and submit a deterministic bid under the intent's deadline, minimum-output and policy constraints.

EXECUTE

Prove and settle

If selected, execute the plan, produce the required receipt/proof and submit settlement before the execution window expires.

M5 rollout gates

  1. DONE: standalone Solver runtime with /healthz, /v1/capabilities, /v1/quote and /v1/execute.
  2. DONE: active/bond eligibility, idempotency, replay-conflict rejection and concurrency backpressure.
  3. DONE: Public Testnet registration package, live registry watcher and operator-signed quote → bid → settlement bridge.
  4. NEXT: one fresh outside Solver identity joins QENOVRA Public Testnet, completes bond lifecycle rehearsal and executes the real end-to-end acceptance path.
  5. Reputation, uptime, rewards and production failure handling.
  6. Multi-node soak testing, recovery and security review.

Why run one?

Solvers are intended to become a competitive execution market. Operators can specialize in liquidity, routing, AI services, cross-chain execution or other capabilities and earn network-defined compensation when they successfully execute eligible intents.

What you will need

A dedicated signing identity, QEN bond on the target network, reliable node connectivity, supported execution adapters, monitoring and operational discipline. Exact M5 public requirements will be frozen before enrollment opens.

See the protocol that already passed

The current Public Testnet evidence includes three Solver registrations, competing bids, deterministic winner B, timeout/slash, fallback to C and real SP1 proof settlement.

View M4.2 evidence ↗ Developer Portal ↗