upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrandon Lucas <thebrandonlucas@gmail.com>2023-02-22 19:14:07 -0500
committerfiatjaf_ <fiatjaf@gmail.com>2023-02-22 21:49:29 -0300
commit2a4c44035e56580fb22929972a69280236663557 (patch)
treed5b9583ec8f29284ee6ee4cd7270ef2bc48cf513
parent050317409d92aaab9007408f4bd5b206cdada1d7 (diff)
Fix minor typo
Fix spelling of `coordinates` in Note
-rw-r--r--04.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/04.md b/04.md
index 0ebcddb..bafc5c7 100644
--- a/04.md
+++ b/04.md
@@ -14,7 +14,7 @@ A special event with kind `4`, meaning "encrypted direct message". It is suppose
14 14
15**`tags`** MAY contain an entry identifying the previous message in a conversation or a message we are explicitly replying to (such that contextual, more organized conversations may happen), in the form `["e", "<event_id>"]`. 15**`tags`** MAY contain an entry identifying the previous message in a conversation or a message we are explicitly replying to (such that contextual, more organized conversations may happen), in the form `["e", "<event_id>"]`.
16 16
17**Note**: By default in the [libsecp256k1](https://github.com/bitcoin-core/secp256k1) ECDH implementation, the secret is the SHA256 hash of the shared point (both X and Y coorinates). In Nostr, only the X coordinate of the shared point is used as the secret and it is NOT hashed. If using libsecp256k1, a custom function that copies the X coordinate must be passed as the `hashfp` argument in `secp256k1_ecdh`. See [here](https://github.com/bitcoin-core/secp256k1/blob/master/src/modules/ecdh/main_impl.h#L29). 17**Note**: By default in the [libsecp256k1](https://github.com/bitcoin-core/secp256k1) ECDH implementation, the secret is the SHA256 hash of the shared point (both X and Y coordinates). In Nostr, only the X coordinate of the shared point is used as the secret and it is NOT hashed. If using libsecp256k1, a custom function that copies the X coordinate must be passed as the `hashfp` argument in `secp256k1_ecdh`. See [here](https://github.com/bitcoin-core/secp256k1/blob/master/src/modules/ecdh/main_impl.h#L29).
18 18
19Code sample for generating such an event in JavaScript: 19Code sample for generating such an event in JavaScript:
20 20