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

Adding additonal author and author's comments re: PSBT version

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

7
90.md
View File

@ -3,13 +3,13 @@ NIP-90
Partially Signed Bitcoin Transactions
--------------------------------------------
`draft` `optional` `author:ronaldstoner` `author:Armin Sabouri` `author:satsie`
`draft` `optional` `author:ronaldstoner` `author:Armin Sabouri` `author:satsie` `author:benthecarman`
# Abstract
This NIP defines an event type for partially signed bitcoin transactions (PSBT) that can be transferred via the Nostr relay network. `1174` is the event kind representing a Bitcoin transaction in standard PSBT format, regardless if the transaction is partially signed or fully finalized.
A special event with kind `1174` which contains an encoded PSBT. PSBTs used under this spec are version 0 [BIP-0174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki).
A special event with kind `1174` which contains an encoded PSBT. PSBTs used under this spec can be any version that conforms to [BIP-0174](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki). Since PSBTs have versioning built in, BIP-0174 recommends bitcoin clients and libraries stop parsing a PSBT if the version is not supported.
PSBTs are encoded as a base64 string, and are contained in the `content` field. These events use a specific kind identifier so that clients do not need to render PSBTs the same as they do notes, invoices, and other event kind identifiers. If clients wish to display PSBTs they can choose to do so in whatever format they wish (string, QR Code, view render).
@ -72,5 +72,4 @@ Note that `pubkey` is a hex-encoded strings.
### Note:
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.