>Notation and Conventions

A short, dense reference. Used consistently throughout the document. Worth a glance now so nothing surprises you later.

a ‖ b

Byte concatenation of a and b.

SHA-256(...)

The standard 32-byte SHA-256 digest of the argument.

rsa_sign(key, msg)
rsa_verify(pubkey, msg, sig)

RSA-PKCS1 or RSA-PSS signature operations.

Tier 1 / 2 / 3 / 4

Hardware tier as defined in Part VIII.6. Tier 1 is CPU; tier 4 is FPGA/ASIC.

task_id

32-byte identifier the coordinator allocates at intake; canonical handle for a unit of work. For ParalleliX AI, one inference request maps to one task_id, dispatched whole.

sub_task_id

32-byte identifier the segmenter allocates per sub-task within a task_id. Used only for genuinely parallelizable workloads that are segmented, not for whole inference requests.

node_id

32-byte identifier derived from SHA-256(node_pubkey).

poe_v1

PoE v1 Proof-of-Execution commitment. Hash form: SHA-256(task_id, result, node_id).

$PRLX

The ERC-20 utility token of the network. Always with the $ prefix.

[Pending deployment]

Used in place of a value not yet locked at the time of writing.

The coordinator

The centralised coordination layer at launch. A federated quorum is a planned later addition, but the term refers to whichever logical entity is acting in the validator role.

The network

The coordination layer plus the node mesh, considered as one running system.

The protocol

The rules and primitives the network enforces; deployment-independent.