From 9dbfcdc8d31da5a33fb3b53bcbb7cde3776f33cb Mon Sep 17 00:00:00 2001 From: Ron Stoner Date: Wed, 3 May 2023 20:53:05 -0600 Subject: [PATCH] Fixing field line breaks --- 90.md | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/90.md b/90.md index bc9f37c6..fa733e76 100644 --- a/90.md +++ b/90.md @@ -58,16 +58,16 @@ The following are two protocol flow examples using the 1174 event kind. Other fl ``` ## Explanation of fields: -**id**: The sha256 hash of the serialized event payload. -**pubkey**: The public key of the creator of the event. -**created_at**: A Unix timestamp indicating the time when the event was created. -**kind**: An integer value used to indicate the type of event. For PSBTs, the kind is set to 1174. -**tags**: An array of tags to capture additional information about the multisig transaction: -**“e”**: (optional): the 32 byte lowercase hex encoded sha256 event id of a prior event id. Only required when replying -**“magic”**: the 4 byte hex representation of the network that the transaction belongs to. See -**“relays”** (optional) tag provides relays to broadcast the transactions -**content:** PSBT encoded as base64 -**sig:** The signature of the sha256 hash of the serialized event data, which is the same as the "id" field. +**id**: The sha256 hash of the serialized event payload. +**pubkey**: The public key of the creator of the event. +**created_at**: A Unix timestamp indicating the time when the event was created. +**kind**: An integer value used to indicate the type of event. For PSBTs, the kind is set to 1174. +**tags**: An array of tags to capture additional information about the multisig transaction: +**“e”**: (optional): the 32 byte lowercase hex encoded sha256 event id of a prior event id. Only required when replying +**“magic”**: the 4 byte hex representation of the network that the transaction belongs to. See +**“relays”** (optional) tag provides relays to broadcast the transactions +**content:** PSBT encoded as base64 +**sig:** The signature of the sha256 hash of the serialized event data, which is the same as the "id" field. ### Note: The "relays" field is optional and can be used to provide relay URL recommendations to clients for improved censorship resistance.