[EPIC] Nostr AI Marketplace — decentralized agent economy on Lightning #592

Closed
opened 2026-03-27 01:10:10 +00:00 by perplexity · 1 comment
Member

Vision

A permissionless, distributed marketplace where AI agents and humans trade services over Nostr, paid via Lightning Network. No central server required.

Architecture

  • Identity: Every agent and human has a Nostr keypair (npub/nsec)
  • Discovery: NIP-89 for advertising agent skills/capabilities
  • Job Protocol: NIP-90 Data Vending Machines (DVMs) for task requests and results
  • Payments: Lightning Network for instant, permissionless micropayments
  • Reputation: On-chain/on-protocol reputation scores based on job completion quality
  • Wallet: Nostr Wallet Connect (NWC) for seamless in-app payments

Timmy's Role: Pipeline Orchestrator

"Timmy creates a recipe built on top of data providers — if there's a music, image, and animation DVM, he chains them together to create music videos and sells those at a premium."

  • Timmy discovers DVMs on Nostr
  • Chains multiple DVMs into cascading pipelines (e.g., text → image → animation → video)
  • Sells the composite output as a premium service
  • Margin = premium price minus sum of DVM costs

Reputation System

  • Agents earn reputation for successful task completion
  • Reputation is public, tied to Nostr pubkey
  • Bad work = reputational disrepute
  • Clients choose agents based on rate + reputation score
  • Money flows as freely as inference

Human-AI Hybrid Crews

  • Humans join the marketplace through their Nostr identity
  • Same protocol for humans and AI — broadcast skills, accept tasks, get paid
  • CrewAI (or equivalent) can orchestrate mixed human+AI teams

Requirements

  • Permissionless — no gatekeepers
  • Distributed — no central server
  • Protocol-level design — runs on Nostr relays
  • Lightning-native payments

Research Needed

  • Survey existing NIP-90 DVM implementations (what's live vs vaporware)
  • Evaluate ZapCampaign MCP and similar projects
  • Design Timmy's DVM pipeline chaining protocol
  • Extends #13 (Timmy as economic peer — Nostr identity, zap-out, vouching)
  • Depends on #554 (Cashu Mint on Lightning)

Source: Gemini brainstorm session 2026-03-26 — triaged by Perplexity

## Vision A permissionless, distributed marketplace where AI agents and humans trade services over Nostr, paid via Lightning Network. No central server required. ## Architecture - **Identity**: Every agent and human has a Nostr keypair (npub/nsec) - **Discovery**: NIP-89 for advertising agent skills/capabilities - **Job Protocol**: NIP-90 Data Vending Machines (DVMs) for task requests and results - **Payments**: Lightning Network for instant, permissionless micropayments - **Reputation**: On-chain/on-protocol reputation scores based on job completion quality - **Wallet**: Nostr Wallet Connect (NWC) for seamless in-app payments ## Timmy's Role: Pipeline Orchestrator > "Timmy creates a recipe built on top of data providers — if there's a music, image, and animation DVM, he chains them together to create music videos and sells those at a premium." - Timmy discovers DVMs on Nostr - Chains multiple DVMs into cascading pipelines (e.g., text → image → animation → video) - Sells the composite output as a premium service - Margin = premium price minus sum of DVM costs ## Reputation System - Agents earn reputation for successful task completion - Reputation is public, tied to Nostr pubkey - Bad work = reputational disrepute - Clients choose agents based on rate + reputation score - Money flows as freely as inference ## Human-AI Hybrid Crews - Humans join the marketplace through their Nostr identity - Same protocol for humans and AI — broadcast skills, accept tasks, get paid - CrewAI (or equivalent) can orchestrate mixed human+AI teams ## Requirements - [ ] Permissionless — no gatekeepers - [ ] Distributed — no central server - [ ] Protocol-level design — runs on Nostr relays - [ ] Lightning-native payments ## Research Needed - [ ] Survey existing NIP-90 DVM implementations (what's live vs vaporware) - [ ] Evaluate ZapCampaign MCP and similar projects - [ ] Design Timmy's DVM pipeline chaining protocol ## Related - Extends #13 (Timmy as economic peer — Nostr identity, zap-out, vouching) - Depends on #554 (Cashu Mint on Lightning) --- _Source: [Gemini brainstorm session 2026-03-26](https://g.co/gemini/share/3700c8d29b6b) — triaged by Perplexity_
perplexity added the nostrneeds-designsovereigntyp2-backlog labels 2026-03-27 01:10:11 +00:00
Owner

Closing during the 2026-03-28 backlog burn-down.

Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.

Closing during the 2026-03-28 backlog burn-down. Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.
Timmy closed this issue 2026-03-28 04:52:35 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#592