Skip to content

Latest commit

 

History

History
63 lines (48 loc) · 1.76 KB

challenges.md

File metadata and controls

63 lines (48 loc) · 1.76 KB

Challenges

Challenges define the evaluation logic for miners. Platform treats challenges as WASM modules with deterministic execution, explicit resource limits, and signed metadata distributed over the validator network.

Challenge Lifecycle

sequenceDiagram
    participant Owner as Sudo Owner
    participant Registry as Challenge Registry
    participant Validators as Validator Set
    participant Runtime as WASM Runtime

    Owner->>Registry: Add/Update/Remove (signed)
    Registry->>Validators: Broadcast metadata
    Validators->>Runtime: Load WASM module
    Runtime-->>Validators: Ready + policy enforcement
    Validators-->>Owner: Consensus-approved state
Loading

Challenge Execution Flow

flowchart TD
    Miner[Miners] -->|Submit payload| P2P[(libp2p gossipsub)]
    P2P --> Validators[Validators]
    Validators --> Runtime[WASM Sandbox]
    Runtime --> Validators
    Validators -->|Scores + votes| P2P
Loading

Runtime Constraints

  • CPU, memory, and I/O quotas enforced per evaluation.
  • Network access allowed only via explicit policy.
  • Deterministic execution required for consensus reproducibility.

Challenge Metadata

Each metadata bundle includes:

  • Challenge identifier + version.
  • WASM module hash and entrypoint.
  • Resource policy (CPU/memory/time limits).
  • Network policy (allowed domains/IPs).
  • Scoring configuration and mechanism mapping.

Challenge States

stateDiagram-v2
    [*] --> Draft
    Draft --> Active: Signed registration
    Active --> Deprecated: New version released
    Deprecated --> Retired: Removed via consensus
    Active --> Retired: Emergency removal
Loading

References