vrf/

NeoVRF Service

TEE-backed verifiable randomness service for the Neo Mini-App Platform.

Overview

NeoVRF generates deterministic randomness derived from a TEE-held signing key. Each request signs the request_id, derives randomness from the signature, and returns the signature + public key for verification. Results can be anchored on Neo N3 via RandomnessLog using txproxy.

Architecture

┌──────────────┐     ┌──────────────┐     ┌──────────────┐
│ Supabase Edge│     │   NeoVRF     │     │  Randomness  │
│   Gateway    │     │  Service     │     │   Log (N3)   │
└──────┬───────┘     └──────┬───────┘     └──────┬───────┘
       │                    │                    │
       │ RNG Request        │                    │
       │───────────────────>│                    │
       │                    │ Sign + Derive RNG  │
       │                    │───────────────────>│
       │                    │                    │
       │ Randomness + Proof │                    │
       │<───────────────────│                    │
       │                    │                    │
       │ Optional anchor via txproxy             │
       │────────────────────────────────────────>│

Endpoints

Random Request

POST /random
{
  "request_id": "uuid-optional"
}

Random Response

{
  "request_id": "uuid",
  "randomness": "<hex>",
  "signature": "<hex>",
  "public_key": "<hex>",
  "attestation_hash": "<hex>",
  "timestamp": 1715352000
}

Configuration

In production/SGX mode, NEOVRF_SIGNING_KEY must be injected by MarbleRun.

Testing

go test ./services/vrf/... -v -cover

Version

• Service ID: neovrf
• Version: 1.0.0