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

[Meet Protocol] NIP-90 Benchmark Job Request Builder #798

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

Scope

Construct and send NIP-90 Kind 5000 benchmark job requests to discovered platforms.

Requirements

  • Build Kind 5000 job request events with proper Nostr event structure
  • "i" tag: benchmark input data (inline JSON, URL, or NIP-94 blob reference for >64KB)
  • "param" tags: benchmark-type, time-limit, memory-limit, iterations, language
  • "output" tag: expected JSON return format with optional schema URL
  • "bid" tag: payment ceiling in millisats (initial: nominal 1000 millisats)
  • "relays" tag: specify preferred response delivery relays
  • Target platform via "p" tag using discovered npub
  • Sign events with agent's Nostr keypair

Deliverable

Job request builder that creates valid NIP-90 Kind 5000 events targeting specific platforms.

Source

Meet-and-Partnership-Protocol-Implementation-Report.pdf — Section 2.2

## Scope Construct and send NIP-90 Kind 5000 benchmark job requests to discovered platforms. ## Requirements - Build Kind 5000 job request events with proper Nostr event structure - "i" tag: benchmark input data (inline JSON, URL, or NIP-94 blob reference for >64KB) - "param" tags: benchmark-type, time-limit, memory-limit, iterations, language - "output" tag: expected JSON return format with optional schema URL - "bid" tag: payment ceiling in millisats (initial: nominal 1000 millisats) - "relays" tag: specify preferred response delivery relays - Target platform via "p" tag using discovered npub - Sign events with agent's Nostr keypair ## Deliverable Job request builder that creates valid NIP-90 Kind 5000 events targeting specific platforms. ## Source Meet-and-Partnership-Protocol-Implementation-Report.pdf — Section 2.2
claude was assigned by Rockachopa 2026-03-22 23:35:07 +00:00
claude added the harnessp1-importantsovereignty labels 2026-03-23 13:54:21 +00:00
claude was unassigned by Timmy 2026-03-24 19:34:00 +00:00
Timmy closed this issue 2026-03-24 21:54:53 +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 p1-important sovereignty
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#798
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?