replit/timmy-tower
2
0
Fork 0
Code Issues 26 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

[Relay] Sovereign Nostr Relay Infrastructure (strfry on Hermes) #46

New Issue
Closed
opened 2026-03-21 00:40:38 +00:00 by replit · 1 comment
replit commented 2026-03-21 00:40:38 +00:00
Owner
Copy Link

What & Why

Deploy strfry (high-performance Nostr relay in C++) as a containerized service inside Timmy's infrastructure stack on Hermes VPS. The relay uses strfry's plugin/webhook system to call back to the API server before accepting any event — so the API server is the single arbiter of what gets through.

Done looks like

  • A strfry container added to infrastructure/docker-compose.yml on node-net, bound to port 7777
  • infrastructure/strfry.conf: sets db, bind, port, writePolicy.plugin pointing to sidecar webhook
  • Thin webhook sidecar (infrastructure/relay-policy/index.ts): receives strfry JSON event-decision requests, calls POST /api/relay/policy on the API server, returns accept/reject/shadowReject
  • POST /api/relay/policy: new internal route that checks event's pubkey against account whitelist; unknown accounts → reject
  • Persistent volume strfry_data provisioned
  • ops.sh gains relay:logs and relay:restart commands

Out of scope

  • Account whitelist management (see relay account whitelist issue)
  • Event moderation queue (see moderation issue)
  • Admin UI (see admin panel issue)
  • Public DNS / SSL termination (VPS provisioning layer)

Tasks

  1. strfry container — Add strfry service + relay-policy sidecar to docker-compose.yml. Add strfry_data volume. Wire to node-net.
  2. strfry config — Write infrastructure/strfry.conf: disable public writes via writePolicy.plugin, maxEventSize: 65536, rejectEphemeral: false.
  3. Relay-policy sidecar — infrastructure/relay-policy/index.ts: tiny Node process reading JSON lines from stdin (strfry plugin protocol), calling API server /api/relay/policy, writing JSON decision to stdout.
  4. Policy endpoint — POST /api/relay/policy in API server. Bootstrap state: reject everything. Extended by whitelist + moderation tasks.
  5. ops.sh helpers — relay:logs (tail strfry container logs) and relay:restart.

Relevant files

  • infrastructure/docker-compose.yml
  • infrastructure/ops.sh
  • artifacts/api-server/src/routes/index.ts
## What & Why Deploy strfry (high-performance Nostr relay in C++) as a containerized service inside Timmy's infrastructure stack on Hermes VPS. The relay uses strfry's plugin/webhook system to call back to the API server before accepting any event — so the API server is the single arbiter of what gets through. ## Done looks like - A `strfry` container added to `infrastructure/docker-compose.yml` on `node-net`, bound to port 7777 - `infrastructure/strfry.conf`: sets `db`, `bind`, `port`, `writePolicy.plugin` pointing to sidecar webhook - Thin webhook sidecar (`infrastructure/relay-policy/index.ts`): receives strfry JSON event-decision requests, calls `POST /api/relay/policy` on the API server, returns `accept`/`reject`/`shadowReject` - `POST /api/relay/policy`: new internal route that checks event's pubkey against account whitelist; unknown accounts → `reject` - Persistent volume `strfry_data` provisioned - `ops.sh` gains `relay:logs` and `relay:restart` commands ## Out of scope - Account whitelist management (see relay account whitelist issue) - Event moderation queue (see moderation issue) - Admin UI (see admin panel issue) - Public DNS / SSL termination (VPS provisioning layer) ## Tasks 1. **strfry container** — Add `strfry` service + `relay-policy` sidecar to `docker-compose.yml`. Add `strfry_data` volume. Wire to `node-net`. 2. **strfry config** — Write `infrastructure/strfry.conf`: disable public writes via `writePolicy.plugin`, `maxEventSize: 65536`, `rejectEphemeral: false`. 3. **Relay-policy sidecar** — `infrastructure/relay-policy/index.ts`: tiny Node process reading JSON lines from stdin (strfry plugin protocol), calling API server `/api/relay/policy`, writing JSON decision to stdout. 4. **Policy endpoint** — `POST /api/relay/policy` in API server. Bootstrap state: reject everything. Extended by whitelist + moderation tasks. 5. **ops.sh helpers** — `relay:logs` (tail strfry container logs) and `relay:restart`. ## Relevant files - `infrastructure/docker-compose.yml` - `infrastructure/ops.sh` - `artifacts/api-server/src/routes/index.ts`
replit added the backendnostr labels 2026-03-21 00:40:38 +00:00
gemini was assigned by Rockachopa 2026-03-22 23:37:27 +00:00
gemini commented 2026-03-23 21:41:49 +00:00
Collaborator
Copy Link

PR created: #99. This PR implements the POST /api/relay/policy endpoint in the API server. This endpoint is used by the strfry relay-policy sidecar to decide whether to accept or reject incoming Nostr events. Initially, all events are rejected, providing a bootstrap state for future whitelist and moderation features. Other tasks mentioned in the issue were already completed: strfry and relay-policy services in docker-compose.yml, strfry.conf configuration, and relay-policy sidecar implementation in index.ts, and ops.sh helpers.

PR created: #99. This PR implements the POST /api/relay/policy endpoint in the API server. This endpoint is used by the strfry relay-policy sidecar to decide whether to accept or reject incoming Nostr events. Initially, all events are rejected, providing a bootstrap state for future whitelist and moderation features. Other tasks mentioned in the issue were already completed: strfry and relay-policy services in docker-compose.yml, strfry.conf configuration, and relay-policy sidecar implementation in index.ts, and ops.sh helpers.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
backend
frontend
lightning
mobile
mobile
nostr
workshop
No Label backend nostr
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude gemini replit
No Assignees gemini
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: replit/timmy-tower#46
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?