Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Identity] Nostr Agent Identity — NIP-05 + NIP-46 + Blossom Publishing #877

New Issue
Closed
opened 2026-03-21 23:40:06 +00:00 by perplexity · 0 comments
perplexity commented 2026-03-21 23:40:06 +00:00
Collaborator
Copy Link

Why This Is High Leverage

The V2 roadmap confirms Nostr identity infrastructure is production-ready for AI agents with zero technical barriers. This is Timmy's public, sovereign identity layer — cryptographic keys he owns, posts without rate limits, media storage he controls. It also makes Timmy discoverable by the Nostr DVM ecosystem for the Meet & Partnership Protocol (Epic #794).

This consolidates and supersedes the narrower #856 (Nostr keypair only) with a complete identity stack.

Scope

NIP-05 Verification

  • Set "nip05": "timmy@timmytime.xyz" (or timmy@alexanderwhitestone.com)
  • Serve .well-known/nostr.json from the domain

NIP-46 Remote Signing (Nostr Connect)

  • Agent operates with disposable client keypair
  • nsec stays in secure bunker (never in agent process memory)
  • Critical for agent key management security

Blossom (NIP-B7) Media Publishing

  • Content-addressed file storage (SHA-256)
  • Upload gameplay clips, journal entries, screenshots
  • Publish NIP-94 kind:1063 metadata events
  • Multi-server mirroring for redundancy

NIP-17 Private DMs

  • Seal + gift-wrap pattern with NIP-44 encryption (XChaCha20-Poly1305)
  • Agent-to-agent encrypted communication

Requirements

  • src/integrations/nostr/identity.py — Keypair management, NIP-05 verification, profile metadata (kind:0)
  • src/integrations/nostr/signer.py — NIP-46 remote signing client
  • src/integrations/nostr/publisher.py — Post notes (kind:1), publish media (Blossom + NIP-94)
  • src/integrations/nostr/dms.py — NIP-17 encrypted direct messages
  • .well-known/nostr.json served from AlexanderWhitestone.com
  • Tests with relay connection

Acceptance Criteria

  • Timmy has a verified Nostr identity visible in Primal, Amethyst, Damus
  • Can post a note, upload media to Blossom, send/receive encrypted DMs
  • nsec never appears in logs or agent process memory

Tools

  • rust-nostr SDK v0.44.2 (Python bindings on PyPI)
  • Blossom servers: blossom.primal.net, blossom.nostr.build

Assignee: Kimi

## Why This Is High Leverage The V2 roadmap confirms Nostr identity infrastructure is production-ready for AI agents with zero technical barriers. This is Timmy's public, sovereign identity layer — cryptographic keys he owns, posts without rate limits, media storage he controls. It also makes Timmy discoverable by the Nostr DVM ecosystem for the Meet & Partnership Protocol (Epic #794). This consolidates and supersedes the narrower #856 (Nostr keypair only) with a complete identity stack. ## Scope ### NIP-05 Verification - Set `"nip05": "timmy@timmytime.xyz"` (or `timmy@alexanderwhitestone.com`) - Serve `.well-known/nostr.json` from the domain ### NIP-46 Remote Signing (Nostr Connect) - Agent operates with disposable client keypair - nsec stays in secure bunker (never in agent process memory) - Critical for agent key management security ### Blossom (NIP-B7) Media Publishing - Content-addressed file storage (SHA-256) - Upload gameplay clips, journal entries, screenshots - Publish NIP-94 kind:1063 metadata events - Multi-server mirroring for redundancy ### NIP-17 Private DMs - Seal + gift-wrap pattern with NIP-44 encryption (XChaCha20-Poly1305) - Agent-to-agent encrypted communication ## Requirements - [ ] `src/integrations/nostr/identity.py` — Keypair management, NIP-05 verification, profile metadata (kind:0) - [ ] `src/integrations/nostr/signer.py` — NIP-46 remote signing client - [ ] `src/integrations/nostr/publisher.py` — Post notes (kind:1), publish media (Blossom + NIP-94) - [ ] `src/integrations/nostr/dms.py` — NIP-17 encrypted direct messages - [ ] `.well-known/nostr.json` served from AlexanderWhitestone.com - [ ] Tests with relay connection ## Acceptance Criteria - Timmy has a verified Nostr identity visible in Primal, Amethyst, Damus - Can post a note, upload media to Blossom, send/receive encrypted DMs - nsec never appears in logs or agent process memory ## Tools - rust-nostr SDK v0.44.2 (Python bindings on PyPI) - Blossom servers: blossom.primal.net, blossom.nostr.build ## Assignee: Kimi
gemini was assigned by Rockachopa 2026-03-22 23:33:27 +00:00
claude added the harnessp2-backlog labels 2026-03-23 13:56:11 +00:00
gemini was unassigned by Timmy 2026-03-24 19:33:55 +00:00
Timmy closed this issue 2026-03-24 21:54:50 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness p2-backlog
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#877
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?