We were including the entire list of prerequisites when generating a shastamp, which for schemas includes the `tools/fromschema.py` doc. This meant all of our shasums were updating anytime this tool file changed. Instead, we just include the first prerequisite. See: https://www.gnu.org/software/make/manual/html_node/Automatic-Variables.html#Automatic-Variables
1.8 KiB
lightning-signpsbt -- Command to sign a wallet's inputs on a provided bitcoin transaction (PSBT).
SYNOPSIS
signpsbt psbt [signonly]
DESCRIPTION
signpsbt is a low-level RPC command which signs a PSBT as defined by BIP-174.
- psbt: A string that represents the PSBT value.
- signonly: An optional array of input numbers to sign.
By default, all known inputs are signed, and others ignored: with signonly, only those inputs are signed, and an error is returned if one of them cannot be signed.
Note that the command will fail if there are no inputs to sign, or if the inputs to be signed were not previously reserved.
EXAMPLE JSON REQUEST
{
"id": 82,
"method": "signpsbt",
"params": {
"psbt": "some_psbt"
}
}
RETURN VALUE
On success, an object is returned, containing:
- signed_psbt (string): The fully signed PSBT
On failure, one of the following error codes may be returned:
- -32602: Error in given parameters, or there aren't wallet's inputs to sign, or we couldn't sign all of signonly, or inputs are not reserved.
EXAMPLE JSON RESPONSE
{
"psbt": "some_psbt"
}
AUTHOR
Vincenzo Palazzo <vincenzo.palazzo@protonmail.com> wrote the initial version of this man page, but many others did the hard work of actually implementing this rpc command.
SEE ALSO
lightning-fundpsbt(7), lightning-sendpsbt(7)
RESOURCES
Main web site: https://github.com/ElementsProject/lightning comment: # ( SHA256STAMP:a64f3742f0c66ddf203afa3f69859d4385c4156fe99c30f0931e41ce95d944b1)