From 8b29b4a3dde88f3330913b3c269733a200c1d801 Mon Sep 17 00:00:00 2001
From: John Heenan <john@zgus.com>
Date: Tue, 17 Sep 2024 09:16:59 +1000
Subject: [PATCH 1/2] Clarify interface of Nostr plugin requesting optional
 private key as it is causing confusion

---
 Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml b/Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml
index a347330..28a9700 100644
--- a/Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml
+++ b/Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml
@@ -48,10 +48,10 @@
 
             </div>
             <div class="form-group">
-                <label asp-for="PrivateKey" class="form-label">Private key for zaps</label>
+                <label asp-for="PrivateKey" class="form-label">Private key for zaps, if you want to prove you issued a receipt</label>
                 <input asp-for="PrivateKey" class="form-control" type="password" value="@Model.PrivateKey"/>
                 <span asp-validation-for="PrivateKey" class="text-danger"></span>
-                <p class="text-muted pt-2">OPTIONALLY, provide the private key to your pubkey so that zaps are signed directly by you as proof of receipt. Supports hex and nsec. Will be converted to hex once saved. </p>
+                <p class="text-muted pt-2">OPTIONALLY, provide the private key to your pubkey so that zaps are signed directly by you as proof of receipt. Otherwise receipts are signed by a random private key that you cannot prove you signed. Supports hex and nsec. Will be converted to hex once saved.</p>
             </div>
             <table class="table table-responsive col-12">
                 <thead>

From 1c2725acd1ee051acdc8d19f1a6b5ceeb0414952 Mon Sep 17 00:00:00 2001
From: John Heenan <john@zgus.com>
Date: Tue, 17 Sep 2024 12:05:47 +1000
Subject: [PATCH 2/2] Add mopre clarifcation about use of lightning address
 with nostr address

---
 Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml b/Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml
index 28a9700..7c0fcde 100644
--- a/Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml
+++ b/Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml
@@ -26,13 +26,13 @@
 
     <partial name="_StatusMessage"/>
 
-    <p class="alert alert-info">For Zaps, just <a class="alert-link" asp-action="EditLightningAddress" asp-controller="UILNURL" asp-route-storeId="@ScopeProvider.GetCurrentStoreId()">enable a lightning address</a>. None of the nostr settings on this page are needed for zaps anymore.</p>
+    <p class="alert alert-info">For Zaps, just <a class="alert-link" asp-action="EditLightningAddress" asp-controller="UILNURL" asp-route-storeId="@ScopeProvider.GetCurrentStoreId()">enable a lightning address</a>. At least one lightning address must exist to receive zaps, even when nostr enabled here. None of the nostr settings on this page are needed for zaps anymore.</p>
 
     <div class="row">
         <div class="col-xl-8 col-xxl-constrain">
             <div class="form-group">
                 <div class="form-group pt-2">
-                    <label asp-for="Name" class="form-label"></label>
+                    <label asp-for="Name (does not need to be same as for a lightning address)" class="form-label"></label>
                     <div class="input-group">
                         <input asp-for="Name" class="form-control"/>
                         <span class="input-group-text">@@@Context.Request.Host.ToUriComponent()@Context.Request.PathBase</span>