Skip to content

Commit e6f2347

Browse files
committed
docs: add Direct Login section — peer-to-peer auth without relay discovery
1 parent 17f54d8 commit e6f2347

2 files changed

Lines changed: 48 additions & 0 deletions

File tree

README.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,24 @@ Level 2 NIP-46 bunker — keys never leave hardware
9696

9797
Products like [NostrKey](https://nostrkey.com) use NSE to protect keys in the browser. NIP-46 bunker signers use NSE on the backend. The principle: **Don't explain cryptography. Explain consequences.**
9898

99+
## Direct Login — No Relay Required
100+
101+
Traditional NIP-46 bunker logins require both sides to connect through a Nostr relay for discovery and message passing. NSE changes that. When the signer is **local** — built into a browser extension or the app itself — signing is a direct, peer-to-peer operation. No relay lookup, no network round-trip, no discovery protocol.
102+
103+
Think of it like an **SSH key**. The key lives on your device. When a site asks you to prove your identity, the extension decrypts and signs locally. The Nostr network isn't involved in the authentication — only in what you do after.
104+
105+
```
106+
Traditional NIP-46 bunker:
107+
App → relay → signer → relay → App
108+
(relay discovery, network latency, relay must be online)
109+
110+
NSE direct login:
111+
App → extension/local signer → App
112+
(peer-to-peer, instant, works offline)
113+
```
114+
115+
For **cross-device** signing (phone as bunker for desktop), you still need a relay — but it can be **your own** relay with a known address. No public relay discovery, no hoping a third-party relay stays online. The connection is direct and deterministic, like pointing SSH at a specific host.
116+
99117
## Repo Structure
100118

101119
```

docs/index.html

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -412,6 +412,36 @@ <h2>NIP Integration</h2>
412412
<p><strong>Future NIP</strong> — Hardware-backed key attestation. Prove to a relay that a key is hardware-protected.</p>
413413
</section>
414414

415+
<section class="section">
416+
<h2>Direct Login — No Relay Required</h2>
417+
<p>
418+
Traditional NIP-46 bunker logins require both sides to connect through a Nostr relay
419+
for discovery and message passing. NSE changes that. When the signer is <strong>local</strong>
420+
built into the browser extension or the app itself — signing is a direct, peer-to-peer
421+
operation. No relay lookup, no network round-trip, no discovery protocol.
422+
</p>
423+
<p>
424+
Think of it like an <strong>SSH key</strong>. The key lives on your device. When a site asks you to
425+
prove your identity, the extension decrypts and signs locally. The Nostr network isn't involved
426+
in the authentication — only in what you do after.
427+
</p>
428+
429+
<div class="flow"><span class="hl">Traditional NIP-46 bunker</span>
430+
App → relay → signer → relay → App
431+
(relay discovery, network latency, relay must be online)
432+
433+
<span class="hl">NSE direct login</span>
434+
App → extension/local signer → App
435+
(peer-to-peer, instant, works offline)</div>
436+
437+
<p>
438+
For <strong>cross-device</strong> signing (phone as bunker for desktop), you still need a relay —
439+
but it can be <strong>your own</strong> relay with a known address. No public relay discovery,
440+
no hoping a third-party relay stays online. The connection is direct and deterministic,
441+
like pointing SSH at a specific host.
442+
</p>
443+
</section>
444+
415445
<section class="section">
416446
<h2>Packages</h2>
417447
<table class="platform-table">

0 commit comments

Comments
 (0)