diff options
| author | Asai Toshiya <to.asai.60@gmail.com> | 2024-02-22 12:30:18 +0900 |
|---|---|---|
| committer | fiatjaf_ <fiatjaf@gmail.com> | 2024-02-22 09:50:12 -0300 |
| commit | 4313fbf7a5c1d7d2c29e414ed68104641f3286fa (patch) | |
| tree | 332b91fc4c43519defabc27cfff90e7d8e7c5095 | |
| parent | cbee1092d25ba60ee3d94de1cc72a8f1efb69070 (diff) | |
NIP-46, NIP-49, NIP-65: fix typos
| -rw-r--r-- | 46.md | 4 | ||||
| -rw-r--r-- | 49.md | 14 | ||||
| -rw-r--r-- | 65.md | 2 |
3 files changed, 10 insertions, 10 deletions
| @@ -96,7 +96,7 @@ nostrconnect://<local-keypair-pubkey>?relay=<wss://relay-to-connect-on>&metadata | |||
| 96 | "pubkey": <local_keypair_pubkey>, | 96 | "pubkey": <local_keypair_pubkey>, |
| 97 | "content": <nip04(<request>)>, | 97 | "content": <nip04(<request>)>, |
| 98 | "tags": [["p", <remote_user_pubkey>]], // NB: in the `create_account` event, the remote signer pubkey should be `p` tagged. | 98 | "tags": [["p", <remote_user_pubkey>]], // NB: in the `create_account` event, the remote signer pubkey should be `p` tagged. |
| 99 | "created_at": <unix timestamp in seconds>, | 99 | "created_at": <unix timestamp in seconds> |
| 100 | } | 100 | } |
| 101 | ``` | 101 | ``` |
| 102 | 102 | ||
| @@ -139,7 +139,7 @@ Each of the following are methods that the client sends to the remote signer. | |||
| 139 | "pubkey": <remote_signer_pubkey>, | 139 | "pubkey": <remote_signer_pubkey>, |
| 140 | "content": <nip04(<response>)>, | 140 | "content": <nip04(<response>)>, |
| 141 | "tags": [["p", <local_keypair_pubkey>]], | 141 | "tags": [["p", <local_keypair_pubkey>]], |
| 142 | "created_at": <unix timestamp in seconds>, | 142 | "created_at": <unix timestamp in seconds> |
| 143 | } | 143 | } |
| 144 | ``` | 144 | ``` |
| 145 | 145 | ||
| @@ -16,13 +16,13 @@ PASSWORD = Read from the user. The password should be unicode normalized to NFKC | |||
| 16 | 16 | ||
| 17 | LOG\_N = Let the user or implementer choose one byte representing a power of 2 (e.g. 18 represents 262,144) which is used as the number of rounds for scrypt. Larger numbers take more time and more memory, and offer better protection: | 17 | LOG\_N = Let the user or implementer choose one byte representing a power of 2 (e.g. 18 represents 262,144) which is used as the number of rounds for scrypt. Larger numbers take more time and more memory, and offer better protection: |
| 18 | 18 | ||
| 19 | | LOG\_N | MEMORY REQUIRED | APPROX TIME ON FAST COMPUTER | | 19 | | LOG_N | MEMORY REQUIRED | APPROX TIME ON FAST COMPUTER | |
| 20 | |--------|-----------------|----------------------------- | | 20 | |-------|-----------------|----------------------------- | |
| 21 | | 16 | 64 MiB | 100 ms | | 21 | | 16 | 64 MiB | 100 ms | |
| 22 | | 18 | 256 MiB | | | 22 | | 18 | 256 MiB | | |
| 23 | | 20 | 1 GiB | 2 seconds | | 23 | | 20 | 1 GiB | 2 seconds | |
| 24 | | 21 | 2 GiB | | | 24 | | 21 | 2 GiB | | |
| 25 | | 22 | 4 GiB | | | 25 | | 22 | 4 GiB | | |
| 26 | 26 | ||
| 27 | SALT = 16 random bytes | 27 | SALT = 16 random bytes |
| 28 | 28 | ||
| @@ -19,7 +19,7 @@ The `.content` is not used. | |||
| 19 | ["r", "wss://alicerelay.example.com"], | 19 | ["r", "wss://alicerelay.example.com"], |
| 20 | ["r", "wss://brando-relay.com"], | 20 | ["r", "wss://brando-relay.com"], |
| 21 | ["r", "wss://expensive-relay.example2.com", "write"], | 21 | ["r", "wss://expensive-relay.example2.com", "write"], |
| 22 | ["r", "wss://nostr-relay.example.com", "read"], | 22 | ["r", "wss://nostr-relay.example.com", "read"] |
| 23 | ], | 23 | ], |
| 24 | "content": "", | 24 | "content": "", |
| 25 | ...other fields | 25 | ...other fields |