DRAFT SPEC

Miner Node Specification v0.1

Draft — December 2024

⚠️ This specification is a draft for v1 internal miners. External miner participation will be defined in v2.

Overview

A Miner Node produces cryptographic proofs that validate or challenge King signals. Miners expend compute to either witness signal stability or find counterexamples.

Proof Types

WITNESS

Demonstrates signal stability by perturbing inputs within epsilon bounds and verifying the signal direction holds.

{
  "type": "WITNESS",
  "eps": 0.03,        // perturbation bound
  "trials": 64,       // number of trials
  "passes": 61,       // trials maintaining signal
  "min_conf": 0.61    // minimum confidence observed
}

COUNTEREXAMPLE

Finds a minimal perturbation that flips the signal direction. Close counterexamples indicate signal fragility.

{
  "type": "COUNTEREXAMPLE",
  "distance": 0.012,  // L2 norm of perturbation
  "delta": {
    "fees": -0.6,
    "mempool": 220
  },
  "flip_to": "SHORT"  // resulting signal direction
}

Requirements

  • Access to Oracle feature extraction pipeline
  • GPU compute for perturbation search (recommended: RTX 3080+)
  • WebSocket connection to signal feed
  • Submission endpoint for proof upload

Submission Flow

  1. Receive signal envelope from /signals WebSocket
  2. Extract features and run perturbation search
  3. Generate proof (WITNESS or COUNTEREXAMPLE)
  4. Submit proof to POST /api/proofs
  5. Receive confirmation and work credit

Roadmap

v0.1Internal miner spec (this document)
v1.0Internal miners operational
v2.0External miner participation, staking, slashing