{ "id": <32-bytes lowercase hex-encoded sha256 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": <integer>, "tags": [ ["e", <32-bytes hex of the id of another event>, <recommended relay URL>], ["p", <32-bytes hex of the key>, <recommended relay URL>], ... // other kinds of tags may be included later ], "content": <arbitrary string>, "sig": <64-bytes hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field> }
Sounds like two fascinating projects. This is clearly a more technical article, which perfectly fine. It depends who your target audience is. My suggestion is, if you'd like to write your articles so that both technical and non-technical can read it better, utiliize chatgpt to create summaries of what you wrote. You can then make the more technical details into sidebars for those who are technically inclined. I'm happy to share with you any chatgpt prompts that I have used in such situations.