NEMES-X

What Happens When You Click "Start Mining"

• Right now: your download starts instantly — early-access preview (1 KB) that reserves your spot.
• At mainnet: the same button delivers the full one-click installer (~2.5GB). Run it once, it auto-detects your GPU/CPU.
• Then: it asks for your TRC20 wallet address (where USDT payouts go) and starts. No account required.

System Requirements

Relative Contribution Power

Multipliers reflect relative embedding throughput, benchmarked on our own 1080 Ti reference rig. Higher multiplier = faster accumulation of work shares.

How Shares Become USDT

Verification Design

• 1 · Random re-check — 10% of all submitted work is independently re-embedded by a random verifier node. If your work is selected, it gets checked.
• 2 · Match requirement — The verifier's output must match yours almost exactly (≥ 99% vector similarity). Same input, same output, same result — no matter the hardware.
• 3 · Tamper-evident assignments — Every job is locked with a digital fingerprint (content hash). You can't alter the task or forge the result.
• 4 · Failed verification — A rejected job burns the worker's shares and the work is re-assigned to another node. Repeated failures lower future job priority.
• 5 · Verifiers are peers — Verifier nodes are ordinary network participants, not privileged insiders. They earn a small fee for verification, and they lose if they lie.

Illustrative Job Record

Example structure — verification engine ships with the ledger phase.

What NEVER Happens

• Your personal files — never scanned, processed, uploaded, or stored. The network has no access to your documents.
• Your local queries — local-mode search runs entirely on your machine. Nothing leaves.
• Raw public corpus text — miners exchange verified vectors, not source documents, in peer sync.
• Your identity — mining does not require a real name, email, or KYC. You are a node ID, nothing more.

What DOES Cross the Network

• Public corpus text — pulled from public sources by miner nodes (the same data anyone can download).
• Vector deltas — int8 embeddings plus scale metadata, content-hashed for integrity.
• Verification proofs — job manifests and similarity attestations, signed by the verifier node.
• Hosted tier (opt-in) — premium queries are processed on our infrastructure; local mode stays local, always. If you do not use the hosted API, your queries never leave your machine.

🟢 TRUE TODAY

• No root / admin required — The pipeline runs as a normal user process. It cannot touch system files or other users' data.
• Hard resource caps — Memory limited to 16GB via systemd MemoryMax, CPU capped at 4 threads, and disk writes bounded by the working directory. If it exceeds any limit, it is killed by the kernel.
• Open pipeline — The entire parse → embed → quantize → merge logic lives in the public repo: parse_documents.py, embed_chunks.py, quantize_vectors.py, merge_indices.py. Inspect them yourself. No black boxes.
• Governance disclosure — Signed epochs can pause or throttle the network. This power is documented openly in the governance section, not hidden in a EULA. You can verify every governance action.

⚪ SHIPPING WITH CLIENT V1

• Sandboxed worker — Containerized execution with filesystem isolation; the miner sees only its working directory and the corpus chunks it is assigned.
• Signed binaries — Every release is cryptographically signed by the founding authority key. Unsigned or tampered clients refuse to run.
• Signed job manifests — Tasks are only accepted from the founding authority key. A forged manifest is rejected before any work begins.
• Reproducible builds — Release artifacts can be rebuilt from source and verified byte-for-byte. Trust, but verify.
• Automatic updates — Signed, rollback-capable. If an update fails verification, the client stays on the last known-good version and alerts the user.

PEER-TO-PEER LAYER

• Miner nodes discover each other directly via libp2p DHT — no central server routes the work.
• Work results and verified vectors propagate peer-to-peer across the network.
• The knowledge index lives across many nodes, not behind a single door. No single server holds the index.

FOUNDING AUTHORITY LAYER

• Task manifests are signed by the founding key. Unsigned work is rejected by design — this is what makes the ledger trustworthy.
• The authority can schedule epochs, throttle workloads, and pause network operations. This is a documented power, not a hidden one.
• Epoch validity is capped at 24 hours. No signed renewal means the network halts by design, not by accident. A dead authority cannot silently keep the network running.
• This power is exercised under the Brain Constitution v1.0 — 12 articles, versioned, changeable only by explicit founder decision. You can read it. You should read it.