Skip to main content

// Section 6.1 · Protocol

Dynamic Node Integration

1 min6.1Protocol
// 1 of 3 · scale model

A node joins by submitting a signed manifest.

// 6.1 · dynamic node integration · no manual whitelist

New nodes join the available pool by staking on-chain through NodeRegistryLocker and submitting a signed capability manifest. The scheduler integrates them immediately. There is no manual whitelist. Node onboarding is permissionless from launch: anyone who stakes the 50,000 $PRLX minimum can register, with no allowlist and no off-site outreach gating.

Join pipeline

// manifest in · pool member out · four stages

01
SIGN MANIFESTThe Node CLI signs liveness heartbeats and results with the node's secp256k1 key (Ethereum personal-sign). It declares the detected tier and capabilities to the coordinator.
02
POST TO INTAKEManifest POST to coordinator /v1/nodes/register endpoint.
03
VERIFY SIGNATURECoordinator validates the signature against the wallet binding. Invalid signatures rejected with no node_id allocated.
04
INTEGRATE POOLCoordinator allocates node_id, writes capability record, node enters READY pool. No human approval step.

Capability manifest shape

// what the node declares · what the coordinator records

// manifest · signed by node.key · pseudocode
{
  "node_pubkey":        "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8...",
  "node_id":            "sha256(node_pubkey)",
  "wallet":             "0x1f3a...",
  "region":             "eu-west",
  "hardware": {
    "tier":             3,
    "cpu_model":        "AMD EPYC 7763",
    "cpu_cores":        128,
    "ram_gb":           512,
    "gpu":              [{ "model": "NVIDIA H100", "count": 4, "vram_gb": 80 }]
  },
  "workload_classes":   ["ai.training", "ai.inference", "media.render"],
  "max_parallel_subtasks": 4,
  "client_version":     "0.1.0",
  "registered_at":      "2026-05-12T14:03:11Z",
  "signature":          "<rsa_sign(manifest)>"
}
// DERIVEDNode identifiernode_id = SHA-256(node_pubkey). No central allocation of names.
// DERIVEDCapability vectorWorkload classes intersected with the active routing policy.
// DERIVEDReputation seedConstant 1.0 at launch. The planned reputation system builds from validated units of work.

Access boundary

// permissionless staking from launch · marketplace + reputation are planned

// AT LAUNCH · PERMISSIONLESS STAKING

Stake and register from launch

  • Anyone who stakes the 50,000 $PRLX minimum can register from day one.
  • registerNode(stakeAmount, hardwareTier, nodeKeyHash) on NodeRegistryLocker. No allowlist, no off-site outreach gate.
  • One stake = one node; unlimited nodes per wallet. No slashing; principal returned in full on unstake.
  • Reputation constant 1.0; enforcement is uptime plus PoE plus sampled re-dispatch.

// PLANNED · OPEN MARKETPLACE

Open submitter marketplace

  • Demand opens beyond ParalleliX AI to third-party submitters.
  • Open compute marketplace with dynamic pricing and SLA enforcement.
  • Reputation system goes live (uptime, completion, validation).
  • Reputation lowers dispatch priority and can drop a node from the active set; it never seizes stake.

What stays the same

// the integration pipeline is the same at every stage

// 01MANIFEST FORMATSame fields, same signature scheme, same intake endpoint at every stage.
// 02DERIVATIONnode_id = SHA-256(node_pubkey). Wallet-bound. Never reassigned.
// 03IMMEDIATE INTEGRATIONAfter signature verification and on-chain stake confirmation, node enters READY pool. No human gate, from launch.
// 04CAPABILITY DISCLOSUREOperators self-declare. Misrepresentation flagged as sybil-adjacent at re-dispatch reconciliation.