Skip to main content
ParalleliX Docs

The Pipeline, in One Diagram

2 minProtocol
// 1 of 2 · task lifecycle

The pipeline, in one diagram

// 3.0 · fourteen steps · ParalleliX AI to operator node

One canonical sequence. Every ParalleliX AI inference request walks it. The order is fixed; the actors do not change roles mid-pipeline. A single inference is autoregressive, so it is dispatched whole to one operator node and served there, never split. Credits are metered off-chain, so there is no per-request on-chain payment. (Segment and aggregate steps exist only for the planned open marketplace, where a genuinely parallelizable job fans out into sub-tasks across nodes.)

// Task lifecycle · 14 stepslive
  1. // 01Request
    ParalleliX AICoordinator

    request(prompt) · credits metered off-chain

  2. // 02Admit
    Coordinator

    check credit balance · alloc request_id

  3. // 03Match
    Coordinator

    match(request) → node_i · capability + uptime

  4. // 04Encrypt
    Coordinator

    encrypt(request, pubkey_i)

  5. // 05Dispatch
    CoordinatorNode N

    dispatch(request) · encrypted envelope · whole to one node

  6. // 06Decrypt
    Node N

    decrypt with node.privkey

  7. // 07Execute
    Node N

    run inference · local GPU / CPU

  8. // 08PoE
    Node N

    PoE = SHA-256(request_id ‖ result ‖ node_id)

  9. // 09Return
    Node NCoordinator

    result + PoE + sig

  10. // 10Verify sig
    Coordinator

    verify sig · reconstruct PoE

  11. // 11Sample
    Coordinator

    sampled re-dispatch → node_j · compare

  12. // 12Anchor
    CoordinatorChain

    ExecutionRecord → chain

  13. // 13Return result
    CoordinatorParalleliX AI

    result streamed back to the user

  14. // 14Settle
    CoordinatorNode N

    credit operator reward weight (uptime) · meter user credits off-chain

Note·Four state-crossing steps

Toxic-accent rows mark the four irreversible boundaries: request ingress, encrypted dispatch, on-chain anchor, operator settle. Everything between them is either local work or recoverable in-protocol.

What the diagram commits to

// 3.0.1 · invariants surfaced by the pipeline shape

  • Credits precede work. No request_id is allocated until the user's off-chain credit balance clears. There is no per-request on-chain payment.
  • Coordinator never holds plaintext mid-transit. Encryption happens before dispatch; only node_i can decrypt the dispatched request.
  • PoE is a commitment, not a proof. Honesty rides on the sampled re-dispatch (step 11), not the hash alone.
  • Anchor before settlement. The execution record commits on-chain (step 12) before the operator's reward weight is credited (step 14).