Formatting fixes

This commit is contained in:
Ron Stoner 2023-05-03 21:02:36 -06:00
parent 9dbfcdc8d3
commit 0efb57f741
No known key found for this signature in database
GPG Key ID: 268C2E2B04CC71D8

22
90.md
View File

@ -58,16 +58,18 @@ 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. ```
**pubkey**: The public key of the creator of the event. id: The sha256 hash of the serialized event payload.
**created_at**: A Unix timestamp indicating the time when the event was created. pubkey: The public key of the creator of the event.
**kind**: An integer value used to indicate the type of event. For PSBTs, the kind is set to 1174. created_at: A Unix timestamp indicating the time when the event was created.
**tags**: An array of tags to capture additional information about the multisig transaction: kind: An integer value used to indicate the type of event. For PSBTs, the kind is set to 1174.
**“e”**: (optional): the 32 byte lowercase hex encoded sha256 event id of a prior event id. Only required when replying tags: An array of tags to capture additional information about the multisig transaction:
**“magic”**: the 4 byte hex representation of the network that the transaction belongs to. See <link to section above that lists magic bytes> “e”: (optional): the 32 byte lowercase hex encoded sha256 event id of a prior event id. Only required when replying.
**“relays”** (optional) tag provides relays to broadcast the transactions “magic”: the 4 byte hex representation of the network that the transaction belongs to.
**content:** PSBT encoded as base64 “relays”: (optional) tag provides relays to broadcast the transactions.
**sig:** The signature of the sha256 hash of the serialized event data, which is the same as the "id" field. 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: ### 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.