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

docs(phase-1): correct FED-05 scope — meshed peers with lightning, not lnd listpeers

Browse Source
This commit is contained in:
archipelago 2026-07-29 11:28:43 -04:00
parent c899ab3591
commit c31d99e49f
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
.planning/phases/01-federation-mesh-hardening/01-CONTEXT.md
View File

@ -9,11 +9,15 @@ neode-ui (Vue), dev preview :8100 against archi-dev.
</domain>
<decisions>
- **FED-05 "public nodes" scope (LOCKED, user 2026-07-29):** the public/other list in the
channel-open picker = any Lightning peer nodes this node is currently connected to
(lnd listpeers), NOT a curated list and NOT a live LN-graph query. Manual URI paste can
remain as a fallback entry path, but the primary lists are: (1) trusted federated nodes
by hostname, (2) connected LN peers.
- **FED-05 "public nodes" scope (LOCKED, user 2026-07-29, corrected same day):** the
public/other list in the channel-open picker = MESHED PEER NODES THAT HAVE LIGHTNING
INSTALLED — nodes known over the mesh (mesh peers/contacts beyond bilateral federation
trust) that advertise lightning capability. NOT lnd listpeers, NOT a curated list, NOT
a live LN-graph query. Implies peers need to advertise a "lightning installed/available"
capability (plus their URI/pubkey) over mesh/federation state so the picker can list
them. Manual URI paste can remain as a fallback entry path. Primary lists: (1) trusted
federated nodes by hostname, (2) meshed peers with lightning installed — "request to
open a channel with" these.
- **FED-05 URI sharing default (Claude's discretion, revisable):** a federated peer's
Lightning URI/pubkey rides the federation sync payload by default — federation trust is
already bilateral and explicit. Follow the existing shared-field pattern in