mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-09-19 14:35:48 -04:00
68c9e484ea
Wrote a note to extension authors
37 lines
1.7 KiB
Markdown
37 lines
1.7 KiB
Markdown
NIP-07
|
|
======
|
|
|
|
`window.nostr` capability for web browsers
|
|
------------------------------------------
|
|
|
|
`draft` `optional` `author:fiatjaf`
|
|
|
|
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.
|
|
|
|
That object must define the following methods:
|
|
|
|
```
|
|
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
|
|
```
|
|
|
|
Aside from these two basic above, the following functions can also be implemented optionally:
|
|
```
|
|
async window.nostr.getRelays(): { [url: string]: {read: boolean, write: boolean} } // returns a basic map of relay urls to relay policies
|
|
async window.nostr.nip04.encrypt(pubkey, plaintext): string // returns 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
|
|
```
|
|
|
|
### Recommendation to Extension Authors
|
|
To make sure that the `window.nostr` is available to nostr clients on page load, the authors who create Chromium and Firefox extensions should load their scripts by specifying `"run_at": "document_end"` in the extension's manifest.
|
|
|
|
|
|
### Implementation
|
|
|
|
- [horse](https://github.com/fiatjaf/horse) (Chrome and derivatives)
|
|
- [nos2x](https://github.com/fiatjaf/nos2x) (Chrome and derivatives)
|
|
- [Alby](https://getalby.com) (Chrome and derivatives, Firefox, Safari)
|
|
- [Blockcore](https://www.blockcore.net/wallet) (Chrome and derivatives)
|
|
- [nos2x-fox](https://diegogurpegui.com/nos2x-fox/) (Firefox)
|
|
- [Flamingo](https://www.getflamingo.org/) (Chrome and derivatives)
|