How super3/llmjob works
LLMJob combines a GPU-node coordination server with LLMJob Earn, an Electron miner and local inference app. The main network workflow is: an operator enrolls a node through Earn; OpenAI-compatible clients submit requests to the server, which routes work to available nodes and returns results. Earn also mines Pearl and can host local LLM inference. The graph preserves those distinct capabilities; several node-worker/server interactions are described only indirectly in the supplied excerpts, so those links are marked unverified.
Main entry points: openaiController.js OpenAI Gateway · main.js Earn Desktop App · routes.js API Routes · jobService.js Job Queue
Components 23
Server API
- API Routes
server/src/routes.js - Node Controller
server/src/controllers/nodeController.js - OpenAI Gateway
server/src/controllers/openaiController.js - Job Controller
server/src/controllers/jobController.js
Node Network
- Node Registry
server/src/services/nodeService.js - Job Queue
server/src/services/jobService.js - Node Job Worker
earn/src/main/jobWorker.js - Node Identity
earn/src/shared/node.js
Earn Mining
- Earn Desktop App
earn/src/main/main.js - Earn CLI
earn/src/cli/earn-cli.js - Pearl Engine
earn/src/main/pearlEngine.js - Pearl Miner
earn/src/main/pearlMiner.js - Native Pearl Core
earn/native/src/pearl_core.cc
Earn Local LLM
- LLM Fleet
earn/src/main/llmFleet.js - LLM Process Manager
earn/src/main/llmManager.js - LLM Engine Setup
earn/src/main/llmEngineManager.js - LLM Runtime Helpers
earn/src/shared/llama.js
Persistence and Usage
- API Key Service
server/src/services/apiKeyService.js - Logs and Usage
server/src/services/logService.js - Postgres
server/src/db.js
Other components
- Operator
- API Client
- Hosted Model Provider
Connections 30
- Operator → Earn Desktop App: uses
README.md - Operator → Earn CLI: uses
README.md - API Client → API Routes: calls API
README.md - API Routes → Node Controller: routes node requests
server/src/routes.js - API Routes → OpenAI Gateway: routes inference requests
server/src/routes.js - API Routes → Job Controller: routes job requests
server/src/routes.js - Node Controller → Node Registry: updates registry
server/src/controllers/nodeController.js - Job Controller → Job Queue: submits and claims
server/src/controllers/jobController.js - OpenAI Gateway → Job Queue: dispatches jobs
server/src/controllers/openaiController.js - OpenAI Gateway → Node Registry: checks node status
server/src/controllers/openaiController.js - OpenAI Gateway → API Key Service: authenticates usage
server/src/controllers/openaiController.js - OpenAI Gateway → Logs and Usage: records usage
server/src/controllers/openaiController.js - OpenAI Gateway → Hosted Model Provider: forwards hosted requests
server/src/controllers/openaiController.js - Operator → API Client: configures
README.md - Earn Desktop App → Pearl Engine: starts mining
earn/src/main/main.js - Pearl Engine → Pearl Miner: starts and observes
earn/src/main/pearlEngine.js - Pearl Miner → Native Pearl Core: runs native mining
- Earn Desktop App → LLM Fleet: manages local inference
earn/src/main/main.js - LLM Fleet → LLM Process Manager: supervises processes
- LLM Process Manager → LLM Runtime Helpers: builds server command
earn/src/main/llmManager.js - LLM Engine Setup → LLM Runtime Helpers: resolves binary
earn/src/main/llmEngineManager.js - Earn Desktop App → LLM Engine Setup: installs inference engine
earn/src/main/main.js - Earn Desktop App → Node Identity: enrolls machine
README.md - Earn CLI → Node Identity: enrolls machine
README.md - Node Job Worker → Job Queue: polls and reports jobs
- Node Job Worker → Node Identity: identifies node
earn/src/main/jobWorker.js - API Key Service → Postgres: reads and writes keys
- Logs and Usage → Postgres: persists usage logs
- Job Queue → Postgres: persists queued work
server/src/services/jobService.js - Node Registry → Postgres: persists node state
server/src/services/nodeService.js