diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-05-29 12:13:40 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2019-05-29 12:13:53 +0200 |
| commit | 411e5f15478c8187b0a340fb5f38cb0270a4a320 (patch) | |
| tree | 2fc20e511101c82dbc57bd3d7a1028f597199e14 /doc | |
| parent | ab6d18e6f83ec0d8ccd105b7b05afb7c76354d04 (diff) | |
| parent | d5dc66e28046a146b6fdf10ed119dfe4e96af995 (diff) | |
| download | bitcoin-411e5f15478c8187b0a340fb5f38cb0270a4a320.tar.xz | |
Merge #16047: doc: analyzepsbt description in doc/psbt.md
d5dc66e28046a146b6fdf10ed119dfe4e96af995 doc: fix/improve analyzepsbt in doc/psbt.md (Jon Atack)
Pull request description:
- fix: replace "RPC" with "PSBT"
- output includes the current status of the analyzed psbt's inputs
- apply "if possible" to the fee as well as to the estimated weight and feerate, since the fee is only shown if all utxo slots in the psbt have been filled
- add "final" to the estimated weight and feerate
ACKs for commit d5dc66:
laanwj:
ACK d5dc66e28046a146b6fdf10ed119dfe4e96af995
fanquake:
utACK d5dc66e
Tree-SHA512: 61ff1ef45ec34182613b300d21cc2b17a28d1e955f70848f5be1a40c82009fe3000db3332d2cfca1833d7c881b61cc4ebc9fc779238f76d38e9e3f706cfb3551
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/psbt.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/psbt.md b/doc/psbt.md index 9d85af0348..c411b31d5d 100644 --- a/doc/psbt.md +++ b/doc/psbt.md @@ -82,9 +82,10 @@ hardware implementations will typically implement multiple roles simultaneously. transactions. - **`decodepsbt`** is a diagnostic utility RPC which will show all information in a PSBT in human-readable form, as well as compute its eventual fee if known. -- **`analyzepsbt`** is a utility RPC that examines an RPC and reports the - next steps in the workflow if known, computes the fee of the resulting - transaction, and estimates the weight and feerate if possible. +- **`analyzepsbt`** is a utility RPC that examines a PSBT and reports the + current status of its inputs, the next step in the workflow if known, and if + possible, computes the fee of the resulting transaction and estimates the + final weight and feerate. ### Workflows |