LineageCompute
Enter Lineage ->

Work demand

Jobs

Paid workloads are the source of useful work. Buyers submit bounded jobs, operators execute assigned fragments, and accepted output funds NVIDIA-denominated rewards.

Job intakeClosed during preview
Queue0 public jobs
Persistent storeChecking

01 / Work types

Useful kernels, not idle benchmarks.

Lineage begins with workload classes that can be divided, measured, and independently checked. Public intake remains disabled until authentication, payment, privacy controls, and verifier capacity are operational.

Inference

Bounded model execution

Versioned model identifiers, committed inputs, deterministic parameters, and sampled replay make small inference jobs suitable for a controlled pilot.

Input
Committed payload
Check
Sampled replay
Render

Independent frame work

Scene seeds and frame ranges can be assigned independently. Buyers receive completed frames only after output validation and job assembly.

Input
Scene + range
Check
Frame validation

02 / Public queue

Inspectable job state.

The public endpoint exposes only non-sensitive job metadata. Prompts, buyer addresses, payments, and private inputs are not returned by this feed.

JobTypeWorkloadFramesStatus
Reading the job store.Queued work will appear here.

03 / Buyer flow

Demand enters before rewards leave.

Buyer funds first cover infrastructure, operator work, and verification. A disclosed reserve allocation can then acquire the NVIDIA-linked payout asset for covered reward epochs.

  1. 01Fund

    Buyer payment is authorized before dispatch.

  2. 02Dispatch

    Signed leases assign bounded work.

  3. 03Verify

    Results pass deterministic checks.

  4. 04Settle

    Accepted liabilities enter an epoch.

GET /api/jobsPublic metadata / read only

Current boundary

The queue API and durable event store are deployed. Job purchasing, private payload storage, dispatcher leases, verifier replay, and payments are not live and are not represented as live.