Fixing field line breaks

This commit is contained in:
Ron Stoner 2023-05-03 20:53:05 -06:00
parent e84d0f2c8a
commit 9dbfcdc8d3
No known key found for this signature in database
GPG Key ID: 268C2E2B04CC71D8

20
90.md
View File

@ -58,16 +58,16 @@ The following are two protocol flow examples using the 1174 event kind. Other fl
``` ```
## Explanation of fields: ## Explanation of fields:
**id**: The sha256 hash of the serialized event payload. **id**: The sha256 hash of the serialized event payload.
**pubkey**: The public key of the creator of the event. **pubkey**: The public key of the creator of the event.
**created_at**: A Unix timestamp indicating the time when the event was created. **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. **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: **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 **“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 <link to section above that lists magic bytes> **“magic”**: the 4 byte hex representation of the network that the transaction belongs to. See <link to section above that lists magic bytes>
**“relays”** (optional) tag provides relays to broadcast the transactions **“relays”** (optional) tag provides relays to broadcast the transactions
**content:** PSBT encoded as base64 **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. **sig:** The signature of the sha256 hash of the serialized event data, which is the same as the "id" field.
### Note: ### Note:
The "relays" field is optional and can be used to provide relay URL recommendations to clients for improved censorship resistance. The "relays" field is optional and can be used to provide relay URL recommendations to clients for improved censorship resistance.