Skip to content

Nuvex is a Solana-native verifiable compute and oracle protocol. Programs accept a job, an input, constraints and a callback. Randomness is the only job the programs fulfill. A read model can list those accounts, and a public price median can be read from the API. Neither copy is chain authority.

3

Solana programs

7

Decision records

80

Byte ECVRF proof

4

Open repositories

Built with open tools and standards

  • Solana
  • Anchor
  • Rust
  • TypeScript
  • PostgreSQL
  • LiteSVM
  • RFC 9381
  • Apache-2.0

One request account carries every job type. Only the randomness path has instructions behind it. Milestone 4 adds an off-chain copy of the accounts that path writes.

Job-agnostic requests

Live

A request carries a job type, an input, constraints and an optional callback. request_randomness is not a program entrypoint.

Verifiable randomness

Live

The verification program checks an RFC 9381 ECVRF proof of 80 bytes and writes the 64-byte output before any callback runs.

Registry and stake

Live

Nodes register a VRF key, lock the configured minimum stake, heartbeat inside a window, and can be slashed by a configured authority.

Indexer and read API

In development

When configured, the indexer copies request, node, registry, protocol and VrfResult accounts. The API and console can list them, including an empty list. The copy is not chain authority.

Price and data jobs

In development

GET /v1/prices returns a median of fresh Coinbase, Kraken, Binance, or Bybit observations. USD and USDT are not mixed. Programs still reject a Price request. Data jobs have no named source check.

Verifiable compute

Planned

Deterministic agreement with commit and reveal is Milestone 6. No compute job runs, and no challenge edge is allowed yet.

AI inference

Research

A commitment to a model and an output is not a proof of correct inference. ADR 0004 says so, and there is no inference runtime.

Each record states a decision, its consequences and the alternatives it rejected. A decision that is not written down is not settled, and the status line on each record says how far it got.

ADR 0001 · Core architectureAccepted, amended in Milestones 1 and 2
ADR 0002 · Account modelLayout specification, amended in Milestone 3
ADR 0003 · Node selectionAmended in Milestone 3, not a weighted lottery
ADR 0004 · Verification modelAccepted for VRF, no audit report found
ADR 0005 · Fee modelA split of roles, numeric parameters unset
ADR 0006 · Callback modelAccepted, empty-account callback only
ADR 0007 · Upgrade modelAccepted as policy, no program deployed

Nothing is shared between them except the decision records and the licence.

nuvex

Protocol

Three Anchor programs, the shared crates, both SDKs, the CLI, the health-only node, the LiteSVM and integration tests, and the security documents.

nuvex-docs

Documentation

The documentation site and the seven decision records. Its contributing guide asks you not to document an instruction, fee or job the protocol has not implemented.

nuvex-web

Website

This site. Console pages can read the configured API. They do not submit transactions, and an API row is not an account.

nuvex-services

Services

The indexer, the HTTP read API, the price adapters that reject every call, and the local compose files. It is not a source of protocol truth.

The README lists these so that the next milestone does not invent them in a pull request that only wants the code to compile.

The VRF audit

The verifier is solana-ecvrf 0.0.1. No audit report was found. ADR 0004 records that absence, and no audit of Nuvex itself has been commissioned.

Challenge, reject and fail edges

Planned

Cancel, expire and VRF fulfilment are the live transitions. ADR 0001 leaves every challenge edge forbidden until it is designed.

Fee shares and selection weights

Planned

The four fee roles exist and the basis points do not. max_fee is stored and never charged. Fulfilment is first-come among eligible nodes, with no weighted lottery.