From 2278d61ebb3fe2e6795d1553f8ca266fd24c1f4e Mon Sep 17 00:00:00 2001
From: thePR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com>
Date: Mon, 27 Oct 2025 10:14:56 -0400
Subject: [PATCH] Document nostr auth providers

---
 docs/nostr-auth.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/docs/nostr-auth.md b/docs/nostr-auth.md
index cc59e1b0..986e7031 100644
--- a/docs/nostr-auth.md
+++ b/docs/nostr-auth.md
@@ -50,10 +50,11 @@ Notes:
 
 `authType` describes how the profile authenticated:
 
-- `"nip07"` – Browser extension flow (current default).
-- `"nsec"` – Reserved for future direct key import or signer integrations. New
-  auth strategies should pick a distinct string and document how migration works
-  alongside any recovery tooling.
+1. `"nip07"` – Browser extension flow that delegates signing to a NIP-07 compatible provider embedded in the browser.
+2. `"nsec"` – Direct key import where the private key stays in the client and bitvid signs locally without an external signer.
+3. `"nip46"` – Remote signer flow that relies on a NIP-46 capable relay or service to authorize requests on behalf of the user.
+
+When introducing additional providers, choose a unique string value and extend this section (plus any related migration notes) to explain how the new strategy authenticates and how existing data should transition.
 
 When the app reads stored entries it normalises unknown values back to
 `"nip07"` but keeps recognised alternatives intact.