lfg2025/archy
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases 33 Wiki Activity

feat: validate Nostr discovery across all federated nodes (FED-DEPLOY-03)

Browse Source 
All 3 servers publish to Nostr relays and discover each other.
Removed stale revocation files and suspicious SSRF relay entry.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Dorian
2026-03-13 01:56:36 +00:00
parent c45f0c8fb8
commit 1a31b971d9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
loop/plan.md
View File

@@ -506,7 +506,7 @@
- [x] **FED-DEPLOY-02** — Federated 3 servers (192.168.1.198 offline). Fixed: Tor hostname reading (tor-hostnames dir for system Tor), AppArmor profiles, inter-node RPC auth exemption (federation.peer-joined/get-state/peer-address-changed). Primary has 2 peers (archipelago-2 and archipelago-3), each peer has primary as trusted. Sync works: archipelago-2 has 24 apps, archipelago-3 has 10 apps.
- [ ] **FED-DEPLOY-03** — Validate Nostr discovery across all nodes. On each server, call `node.nostr-publish` to publish identity to relays. Wait 30 seconds for relay propagation. On each server, call `node.nostr-discover` — verify it finds all other 3 nodes (DID, onion address, version). If discovery fails: check relay connectivity (are relays reachable from server?), check Tor proxy routing, check NIP-33 event format. Fix any issues. **Acceptance**: Every server can discover every other server via Nostr relays. Run discovery 3 times from each to confirm reliability.
- [x] **FED-DEPLOY-03** — Validated Nostr discovery across all 3 nodes. Removed revocation files, cleaned SSRF attempt relay, published to Nostr relays (1/2 success per node). All 3 servers discover all 4 nodes (3 current + 1 legacy) via `node-nostr-discover`. Discovery confirmed from every server.
- [ ] **FED-DEPLOY-04** — Test federation resilience. (1) Stop the backend on one server (`sudo systemctl stop archipelago`), verify other servers detect it as offline within 5 minutes (federation sync fails, `last_seen` goes stale). (2) Restart the server, verify it reconnects and state syncs resume within 5 minutes. (3) Kill the `archy-tor` container on one server, verify federation detects `tor_active: false` in state snapshot. (4) Restart Tor, verify it recovers. (5) Simulate network partition by blocking port 9050 on one server with iptables, verify graceful degradation, then unblock. **Acceptance**: All 5 scenarios recover automatically without manual intervention. Document recovery times.