NAP-NEIGHBOR: Peer-Carried Neighborhoods (Proposed)
NAP-NEIGHBOR is an open draft napplet proposal, #146. NAPs are napplet draft contracts, not accepted NIPs. The proposal gives each napplet opaque neighborhood addresses for the relay, outbox, resource and upload domains. Traffic for these addresses travels over the user’s own peers. Each user has their own view of their peers. The host manages the neighborhood and keeps each napplet’s addresses separate. Sharing proximity information and napplet updates is optional.
A neighborhood has no membership list and no privacy boundary. Any peer can pass ordinary Nostr events on to others. The specifications that consume these addresses would need scheme changes, and upload use would need defined destinations. No transport implementation has been verified, and nothing guarantees delivery or reach. The companion registry change #147 is part of this proposal. NAP-NEIGHBOR follows the mesh drafts #122 and #123, which were retracted.
Primary sources:
Mentioned in:
See also: