// Section 2.3 · Concepts
The node client
The only piece an operator runs locally.
// 2.3 · the node client · linux x86_64 first
The node client is the software an operator installs on their machine. It is the only piece of the system the operator runs locally. Linux x86_64 ships first; other targets follow capability demand.
Eight responsibilities
// key generation through status reporting
Generate and protect the node's secp256k1 key (a separate liveness key). Mode 0600 enforced.
Compute and submit the hardware capability manifest. Signed.
Maintain a persistent connection to the coordinator. Heartbeat every 30s.
Decrypt dispatched work payloads with the local private key.
Execute the dispatched unit of work against the local GPU / CPU. An AI inference request runs whole; a parallelizable sub-task runs its slice.
Compute SHA-256(task_id || result || node_id) for each result.
Sign and return results to the coordinator.
Surface local state: READY · EXECUTING · IDLE · UNSTAKING.
The capability manifest
// signed by node.key · submitted at registration
{
"node_id": "0x...",
"wallet_address": "0x...",
"pubkey_rsa": "-----BEGIN PUBLIC KEY-----...",
"hardware_tier": 3,
"cpu": { "model": "EPYC 7763", "cores": 128, "ram_gb": 512 },
"gpu": [{ "model": "NVIDIA H100", "count": 4, "vram_gb": 80 }],
"region": "eu-west",
"workload_classes": ["ai.training", "ai.inference", "media.render"],
"max_parallel_subtasks": 4,
"client_version": "0.1.0",
"signature": "rsa(0x...)"
}The coordinator verifies the signature against the declared public key and checks the wallet for prior registrations (sybil pre-screen).
Local states
// four states · log events tagged state.transition