Response has all elements needed to check and verify. New method name to avoid backwards incompatibility in the wild

This commit is contained in:
Rob Woodgate 2025-03-19 22:37:51 +00:00
parent 39bf3cdbea
commit fdb31772a0
2 changed files with 2 additions and 2 deletions

2
07.md
View File

@ -21,7 +21,7 @@ async window.nostr.nip04.encrypt(pubkey, plaintext): string // returns ciphertex
async window.nostr.nip04.decrypt(pubkey, ciphertext): string // takes ciphertext and iv as specified in nip-04 (deprecated)
async window.nostr.nip44.encrypt(pubkey, plaintext): string // returns ciphertext as specified in nip-44
async window.nostr.nip44.decrypt(pubkey, ciphertext): string // takes ciphertext as specified in nip-44
async window.nostr.signSchnorr(message: string): string // Returns `sig` for the SHA256 hash of `message`
async window.nostr.signString(message: string): { hash: string, sig: string, pubkey: string } // return SHA256 `hash` of `message`, Schnorr `sig` of `hash`, `pubkey` of signer
```
### Recommendation to Extension Authors

2
46.md
View File

@ -105,7 +105,7 @@ Each of the following are methods that the _client_ sends to the _remote-signer_
| `nip04_decrypt` | `[<third_party_pubkey>, <nip04_ciphertext_to_decrypt>]` | `<plaintext>` |
| `nip44_encrypt` | `[<third_party_pubkey>, <plaintext_to_encrypt>]` | `<nip44_ciphertext>` |
| `nip44_decrypt` | `[<third_party_pubkey>, <nip44_ciphertext_to_decrypt>]` | `<plaintext>` |
| `sign_schnorr` | `[<message_string_to_sign>]` | `<sig_for_sha256_hash_of_message>` |
| `sign_string` | `[<message_string_to_sign>]` | `json_stringified({ hash: <sha256_of_message>, sig: <schnorr_of_hash>, pubkey: <pubkey> })` |
### Requested permissions