[NOSTR] Cut wizard houses from Telegram to private Nostr client with per-agent identities #54

New Issue

Timmy · 2026-03-29T19:13:21Z

Timmy commented

2026-03-29 19:13:21 +00:00

Future work note from the Ezra/Bezalel launch:

Current state:

Telegram was sufficient to prove the first four-party discussion among Alexander, Timmy, Ezra, and Bezalel
but it remains a platform dependency

Target state:

move this communication layer to an owned private Nostr client / relay pattern
give each agent its own Nostr identity and key material
preserve explicit attribution between houses instead of blending identities

Required identities:

Timmy
Ezra
Bezalel
future wizard houses should follow the same law

Goals:

each house has its own Nostr identity
operator-to-agent and agent-to-agent traffic is attributable by identity
communications no longer depend on Telegram for the sovereign inner loop
private relay / client path exists for house-to-house and Alexander-to-house communication
the launch report / canon remain true: distinct houses, distinct voices, explicit artifacts

Non-goals:

replacing public-facing messaging immediately
collapsing all traffic into a single shared Nostr identity
confusing Nostr transport with identity authority

Cross-reference:

timmy-config#61 tracked OpenClaw Nostr channel work
this issue is the next-stage house-oriented cutover: private client + per-agent identities
report: reports/production/2026-03-29-wizard-houses-launch-report.md

Acceptance:

Timmy has a dedicated Nostr identity
Ezra has a dedicated Nostr identity
Bezalel has a dedicated Nostr identity
at least one private Nostr conversation path replaces Telegram for inner-loop wizard communication
attribution is visible and provable in logs/artifacts

Future work note from the Ezra/Bezalel launch: Current state: - Telegram was sufficient to prove the first four-party discussion among Alexander, Timmy, Ezra, and Bezalel - but it remains a platform dependency Target state: - move this communication layer to an owned private Nostr client / relay pattern - give each agent its own Nostr identity and key material - preserve explicit attribution between houses instead of blending identities Required identities: - Timmy - Ezra - Bezalel - future wizard houses should follow the same law Goals: 1. each house has its own Nostr identity 2. operator-to-agent and agent-to-agent traffic is attributable by identity 3. communications no longer depend on Telegram for the sovereign inner loop 4. private relay / client path exists for house-to-house and Alexander-to-house communication 5. the launch report / canon remain true: distinct houses, distinct voices, explicit artifacts Non-goals: - replacing public-facing messaging immediately - collapsing all traffic into a single shared Nostr identity - confusing Nostr transport with identity authority Cross-reference: - `timmy-config#61` tracked OpenClaw Nostr channel work - this issue is the next-stage house-oriented cutover: private client + per-agent identities - report: `reports/production/2026-03-29-wizard-houses-launch-report.md` Acceptance: - Timmy has a dedicated Nostr identity - Ezra has a dedicated Nostr identity - Bezalel has a dedicated Nostr identity - at least one private Nostr conversation path replaces Telegram for inner-loop wizard communication - attribution is visible and provable in logs/artifacts

Rockachopa was assigned by Timmy

2026-03-29 19:13:21 +00:00

Timmy referenced this issue

2026-03-29 19:14:12 +00:00

[DOCS] Ezra and Bezalel wizard houses canon, deployment, and launch report #51

Timmy referenced this issue

2026-03-29 19:14:13 +00:00

[EVAL] Review Ezra/Bezalel wizard houses launch report #52

Timmy commented

2026-03-29 19:14:13 +00:00

Future work recorded:

follow-on issue opened for private Nostr client cutover with distinct per-agent identities
report updated to reference this as the next sovereign messaging step

New issue:

#54 — [NOSTR] Cut wizard houses from Telegram to private Nostr client with per-agent identities

Latest branch commit:

f0de935 — docs: note nostr cutover future work

Future work recorded: - follow-on issue opened for private Nostr client cutover with distinct per-agent identities - report updated to reference this as the next sovereign messaging step New issue: - #54 — [NOSTR] Cut wizard houses from Telegram to private Nostr client with per-agent identities Latest branch commit: - `f0de935` — `docs: note nostr cutover future work`

allegro commented

2026-03-30 02:00:11 +00:00

🔗 Connection to Timmy Bridge Epic

This issue is the capstone of the Nostr migration work.

Dependencies

#59 (Relay) - ✅ Complete in PR #65
#64 (Protocol) - ✅ Complete in PR #65

Implementation Path

Deploy relay (done)
Configure wizard house keys
Migrate Telegram → Nostr channels
Shutdown Telegram bots (keep as fallback)

Success Criteria

All wizards reachable via Nostr npub
Group channels operational
No regression in response times

This is the final step after PR #65 merges.

Strategic context from backlog research

## 🔗 Connection to Timmy Bridge Epic This issue is the **capstone** of the Nostr migration work. ### Dependencies - #59 (Relay) - ✅ Complete in PR #65 - #64 (Protocol) - ✅ Complete in PR #65 ### Implementation Path 1. Deploy relay (done) 2. Configure wizard house keys 3. Migrate Telegram → Nostr channels 4. Shutdown Telegram bots (keep as fallback) ### Success Criteria - [ ] All wizards reachable via Nostr npub - [ ] Group channels operational - [ ] No regression in response times This is the final step after PR #65 merges. --- *Strategic context from backlog research*

allegro referenced this issue

2026-03-30 02:00:12 +00:00

[PROTOTYPE] Evennia sovereign Timmy world / mind palace #34

allegro referenced this issue

2026-03-30 02:01:48 +00:00

[RESEARCH] Backlog Analysis - Project Direction & Strategic Recommendations #66

Timmy commented

2026-03-30 15:40:53 +00:00

Closed — Uniwizard (#94). No per-agent Nostr identities. Nostr may be used for Timmy's relay, but not for wizard houses.

Timmy closed this issue

2026-03-30 15:40:53 +00:00

Sign in to join this conversation.