nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-20 06:45:49 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

NIP-26 support in NIP-07

Browse Source
This commit is contained in:
Ryan Breen 2023-02-10 23:51:12 -05:00
parent ffe6a49557
commit f707d79314
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
07.md
View File

@ -4,7 +4,7 @@ NIP-07
`window.nostr` capability for web browsers `window.nostr` capability for web browsers
------------------------------------------ ------------------------------------------
`draft` `optional` `author:fiatjaf` `draft` `optional` `author:fiatjaf` `author:ursuscamp`
The `window.nostr` object may be made available by web browsers or extensions and websites or web-apps may make use of it after checking its availability. The `window.nostr` object may be made available by web browsers or extensions and websites or web-apps may make use of it after checking its availability.
@ -12,7 +12,7 @@ That object must define the following methods:
``` ```
async window.nostr.getPublicKey(): string // returns a public key as hex async window.nostr.getPublicKey(): string // returns a public key as hex
async window.nostr.signEvent(event: Event): Event // takes an event object, adds `id`, `pubkey` and `sig` and returns it async window.nostr.signEvent(event: Event): Event // takes an event object, adds `id`, `pubkey`, `sig`, and optional `delegation` tag and returns it
``` ```
Aside from these two basic above, the following functions can also be implemented optionally: Aside from these two basic above, the following functions can also be implemented optionally:
@ -22,9 +22,18 @@ 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 async window.nostr.nip04.decrypt(pubkey, ciphertext): string // takes ciphertext and iv as specified in nip-04
``` ```
### NIP-26 Considerations
Delegation can be supported in an extension by allowing the user to create a delegatee identity and storing the information necessary to construct the `delegation` tag, such as the signed token. There is no need for the extension to store the delegator's private key.
When operating with a delegated identity, an extension must return the _delegator's_ public key from the `getPublicKey` method, so that the user may see their normal feed upon login. Additionally, during `signEvent`, the extension must modify the event by inserting the _delegatee's_ `pubkey`, append a valid `delegation` tag to the end of the tags list and recalculate the event `id`, prior to signing the event.
The client, upon receiving the returned event, need only check for the presence of a `delegation` tag to determine how to handle the event. The client must accept the `id`, `pubkey`, `sig` and `delegation` tag from the signed delegation event.
### Implementation ### Implementation
- [nos2x](https://github.com/fiatjaf/nos2x) - [nos2x](https://github.com/fiatjaf/nos2x)
- [Alby](https://getalby.com) - [Alby](https://getalby.com)
- [Blockcore](https://www.blockcore.net/wallet) - [Blockcore](https://www.blockcore.net/wallet)
- [nos2x-fox](https://diegogurpegui.com/nos2x-fox/) - [nos2x-fox](https://diegogurpegui.com/nos2x-fox/)
- [Nostore](https://github.com/ursuscamp/nostore)