From d0812229a5569372a6cd1bdb8d148beb1820585d Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Sun, 21 Jan 2024 16:08:45 -0300 Subject: use jsonc in some places. --- 01.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to '01.md') diff --git a/01.md b/01.md index 80ee792..46316ea 100644 --- a/01.md +++ b/01.md @@ -14,7 +14,7 @@ Each user has a keypair. Signatures, public key, and encodings are done accordin The only object type that exists is the `event`, which has the following format on the wire: -```json +```jsonc { "id": <32-bytes lowercase hex-encoded sha256 of the serialized event data>, "pubkey": <32-bytes lowercase hex-encoded public key of the event creator>, @@ -22,7 +22,7 @@ The only object type that exists is the `event`, which has the following format "kind": , "tags": [ [...], - ... + // ... ], "content": , "sig": <64-bytes lowercase hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field> @@ -58,17 +58,16 @@ To prevent implementation differences from creating a different event ID for the Each tag is an array of strings of arbitrary size, with some conventions around them. Take a look at the example below: -```json +```jsonc { - ..., "tags": [ ["e", "5c83da77af1dec6d7289834998ad7aafbd9e2191396d75ec3cc27f5a77226f36", "wss://nostr.example.com"], ["p", "f7234bd4c1394dda46d09f35bd384dd30cc552ad5541990f98844fb06676e9ca"], ["a", "30023:f7234bd4c1394dda46d09f35bd384dd30cc552ad5541990f98844fb06676e9ca:abcd", "wss://nostr.example.com"], ["alt", "reply"], - ... + // ... ], - ... + // ... } ``` -- cgit v1.2.3