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] 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>