Compare commits

...

3 Commits

Author SHA1 Message Date
fiatjaf_
9fcff79cfd change kind of community post from 1 to 72 2023-10-28 06:46:33 -03:00
Mike O'Bank
ca73c5dd5e Clarify Unsigned Event Object type 2023-10-21 16:05:32 -03:00
Egge
4216f0bf2f added nodestr 2023-10-19 14:32:41 -03:00
2 changed files with 3 additions and 2 deletions

3
07.md
View File

@@ -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.signEvent(event: Event): Event // takes an event object, adds `id`, `pubkey` and `sig` and returns it
async window.nostr.signEvent(event: { created_at: number, kind: number, tags: string[][], content: string }): 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:
@@ -34,3 +34,4 @@ async window.nostr.nip04.decrypt(pubkey, ciphertext): string // takes ciphertext
- [TokenPocket](https://www.tokenpocket.pro/) (Android, IOS, Chrome and derivatives)
- [Nostrmo](https://github.com/haorendashu/nostrmo_faq#download) (Android, IOS)
- [Spring Browser](https://spring.site) (Android)
- [nodestr](https://github.com/lightning-digital-entertainment/nodestr) (NodeJS polyfill)

2
72.md
View File

@@ -48,7 +48,7 @@ Any Nostr event can be a post request. Clients MUST add the community's `a` tag
"id": "<32-bytes lowercase hex-encoded SHA-256 of the the serialized event data>",
"pubkey": "<32-bytes lowercase hex-encoded public key of the event creator>",
"created_at": <Unix timestamp in seconds>,
"kind": 1,
"kind": 72,
"tags": [
["a", "34550:<Community event author pubkey>:<d-identifier of the community>", "<Optional relay url>"],
],