Inference you can use. Identity no one can follow.
LLUMA is a torrent-style network for running language-model inference across volunteer hosts. Prompts and identity enter the network on opposite sides and meet only inside an untraceable core: the host that serves your content never learns who asked, and the host that knows who asked never sees the content. No accounts. No logs worth seizing. Zero external requests on this page — view source.
§ 01Architecture
LLUMA-SPEC-001 · REV 2Three roles, strictly separated. Anonymity is not a feature bolted on top — it is the consequence of no single party ever holding both halves of a request.
| Role | Function | Sees | Never sees |
|---|---|---|---|
| RELAY | Routes encrypted frames between peers. Interchangeable, unprivileged. | sees: ciphertext | content · identity |
| BROKER | Matches inference demand to host capacity. Holds session tokens, not sessions. | sees: capacity, tokens | prompt content · client address |
| HOST | Executes inference on volunteered hardware. Paid in network credit. | sees: plaintext prompt | who asked · origin, account, address |
§ 02Operation
LLUMA-SPEC-001 · REV 2One request, end to end. Order matters; the sequence below is the protocol.
- Client splits the request. Identity material goes to the identity path; the prompt is encrypted to the content path. The two halves share only a one-time pairing token.
- Broker matches capacity. A host advertising free compute is assigned by token. The broker never receives the prompt and never learns the client's address.
- Relays carry ciphertext. Frames hop across volunteer relays torrent-style. Any relay sees traffic; no relay sees meaning.
- Host runs inference. The prompt decrypts only on the assigned host. Output returns along a fresh relay path — never the inbound one.
- The pairing token burns. After delivery the token is destroyed. There is no durable record linking identity to content — nothing to subpoena, nothing to leak.
§ 03Trust model
LLUMA-SPEC-001 · REV 2Two tiers, honestly labeled. The Open tier is not zero-knowledge — the executing host sees your plaintext prompt without knowing who sent it. If host-blindness is a requirement, use the Confidential tier.
| Tier | Execution | Host sees | Guarantee |
|---|---|---|---|
| OPEN | Any volunteer host | plaintext prompt, anonymous origin | Unlinkability — content cannot be traced to identity |
| CONFIDENTIAL | tier: tee — attested enclave hosts | sees: ciphertext | Unlinkability + host-blindness, verified by remote attestation |
§ 04Contribution
LLUMA-SPEC-001 · REV 2The network is its volunteers. Contribute what you have; earn network credit against future inference.
| Contribute | Requirement | Earns |
|---|---|---|
| RELAY | Stable uplink, any hardware | ★★★ |
| BROKER | High-availability node, staked credit | ★★★ |
| HOST — OPEN | GPU with ≥16 GB VRAM | ★★★ |
| HOST — TEE | Attestation-capable enclave hardware | ★★★ |