aljaz/BTCPayServerPlugins
1
0
Fork 0
mirror of https://github.com/aljazceru/BTCPayServerPlugins.git synced 2025-12-17 07:34:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

Clarify interface of Nostr plugin requesting optional private key as it is causing confusion

Browse Source
This commit is contained in:
John Heenan
2024-09-17 09:16:59 +10:00
parent 5cfe2e5acd
commit 8b29b4a3dd
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Plugins/BTCPayServer.Plugins.NIP05/Views/Nip5/Edit.cshtml
View File

@@ -48,10 +48,10 @@
</div> </div>
<div class="form-group"> <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"/> <input asp-for="PrivateKey" class="form-control" type="password" value="@Model.PrivateKey"/>
<span asp-validation-for="PrivateKey" class="text-danger"></span> <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> </div>
<table class="table table-responsive col-12"> <table class="table table-responsive col-12">
<thead> <thead>