BuyBitcoinNow on Nostr: Example of how events are saved: { "id": "", "pubkey": "", "created_at": , "kind": , ...
Example of how events are saved:
{
"id": "",
"pubkey": "",
"created_at": ,
"kind": ,
"tags": [],
"content": "",
"sig": ""
}
The id field tells us the ID of the event.
The pubkey field tells us the public key of the user who sent the event.
The created_at field tells us when the event was published.
The kind field tells us what sort of event it is.
The tags field tells us about tags on the event. These are used for creating links, adding media, and mentioning other users or events.
The content field gives us the content of the event. In this case, the short text post.
The sig field is the signature that clients use to verify that the user with this pubkey did in fact send this event on the date specified.
{
"id": "",
"pubkey": "",
"created_at": ,
"kind": ,
"tags": [],
"content": "",
"sig": ""
}
The id field tells us the ID of the event.
The pubkey field tells us the public key of the user who sent the event.
The created_at field tells us when the event was published.
The kind field tells us what sort of event it is.
The tags field tells us about tags on the event. These are used for creating links, adding media, and mentioning other users or events.
The content field gives us the content of the event. In this case, the short text post.
The sig field is the signature that clients use to verify that the user with this pubkey did in fact send this event on the date specified.