mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-27 18:55:52 -05:00
Formatting fixes
This commit is contained in:
parent
9dbfcdc8d3
commit
0efb57f741
22
90.md
22
90.md
|
@ -58,16 +58,18 @@ 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 <link to section above that lists magic bytes>
|
||||
**“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.
|
||||
“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.
|
||||
|
|
Loading…
Reference in New Issue
Block a user