nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-27 02:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updating content field from b64 -> hex

Browse Source
This commit is contained in:
Ron Stoner 2023-05-11 08:00:18 -06:00
parent a5e35fdcdf
commit cd56ffb329
No known key found for this signature in database
GPG Key ID: 268C2E2B04CC71D8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
90.md
View File

@ -52,7 +52,7 @@ The following are two protocol flow examples using the 1174 event kind. Other fl
[“magic”, <4-byte hex value representing the Bitcoin network identifier>], [“magic”, <4-byte hex value representing the Bitcoin network identifier>],
[“relays”, <list of relays to broadcast event>], [“relays”, <list of relays to broadcast event>],
], ],
"content": <base 64 encoded PSBT>, "content": <hex encoded PSBT>,
"sig": <64-bytes hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field> "sig": <64-bytes hex of the signature of the sha256 hash of the serialized event data, which is the same as the "id" field>
} }
``` ```
@ -72,4 +72,4 @@ Note that `pubkey` is a hex-encoded strings.
### Note: ### Note:
The "e" field is optional and is used when replying to a prior event. The "e" field is optional and is used when replying to a prior event.
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.