Status: Draft v0.1 · An encrypted inference marketplace
A blind, end-to-end-encrypted marketplace for LLM inference, paid in bitcoin, built on the NUTS ecosystem. Providers run Ollama and choose which models to sell. Consumers run any coding agent (via Nemesis8) against those models. A central gateway authenticates both sides with NUTS tokens, matches them, relays opaque ciphertext, settles payment, and takes a fee — without ever seeing a prompt or a reply.
- A provider runs Ollama and picks models to share. See 06-provider.md.
- A consumer uses Nemesis8 to fire up any coding agent and point it at a shared model. See 07-consumer-nemesis8.md.
| # | Document | What it covers |
|---|---|---|
| 00 | overview | Goals, actors, principles, glossary, non-goals |
| 01 | architecture | Topology, planes, request lifecycle, trust boundaries |
| 02 | identity-auth | NUTS tokens, the per-identity static key, pinning |
| 03 | wire-protocol | Tunnel frames, the cleartext envelope, correlation |
| 04 | encryption | Noise handshake, AEAD, envelope binding, MITM defense |
| 05 | payments | Pricing, rails, the fee cut, settlement, double-blind |
| 06 | provider | Provider proxy, Ollama, model-share config |
| 07 | consumer-nemesis8 | Consumer proxy, OpenAI surface, Nemesis8 wiring |
| 08 | discovery-reputation | Directory, BARKER, portable signed ratings |
| 09 | gateway | Blind-relay responsibilities, state, rate limits |
| 10 | security-threat-model | Threats, mitigations, residual risk |
| 11 | deployment | Container roster, Cloud Run (nuts.services), auth wiring |
| 12 | ui-dashboard | Web UI: NUTS login, provider ads, payments; gateway HTTP API |
| 13 | mcp | MCP server: buy inference as tools; 402 pay-required with ASCII-QR invoice |
| 14 | compute | Draft/roadmap — training & GPU-rental jobs: lifecycle, escrow, the (non-blind) privacy caveat |
| 15 | approval-console | Draft — local Charon Client: approval gate, audit log + search, dashboard link |
The key words MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY are used as in RFC 2119. JSON is the canonical encoding for control messages. All sizes are bytes unless noted; all monetary amounts are millisatoshis (msat) on the wire.
A Rust workspace scaffold (charon) exists with the gateway, the
provider proxy, the shared wire types, and stubbed payment rails. These specs
are the authoritative description; the scaffold is one implementation in
progress. Where they disagree, the spec wins.