merge Bitcoin #16325 #16210 #15784 #15757 : Backport#4613
merge Bitcoin #16325 #16210 #15784 #15757 : Backport#4613UdjinM6 merged 4 commits intodashpay:developfrom
Conversation
350423a to
33cd5f5
Compare
d55180d to
867371b
Compare
|
64 bit Test Failed due to Disk space |
|
Hello @UdjinM6 requesting review |
|
Hello @PastaPastaPasta , Requesting review |
|
This pull request has conflicts, please rebase. |
29bb873 to
59d4b0a
Compare
c0d1304 to
bc302ae
Compare
|
This Pull Request may conflict if the Pull Requests below are merged first. #4643 |
9b085f4 Mention new descriptor RPCs in descriptors.md (Pieter Wuille) 28d78de Mention new PSBT RPCs in psbt.md (Pieter Wuille) Pull request description: The documentation in `psbt.md` and `descriptors.md` does not list new and updated RPCs (`analyzepsbt`, `utxoupdatepsbt`, `joinpsbts`, `deriveaddresses`, `getdescriptorinfo`, `listunspent`). Fix this. It'd be good to have this in 0.18 (only documentation). ACKs for commit 9b085f: fanquake: utACK 9b085f4 Tree-SHA512: ee16907e8c15351a530f11fc0a585c50835a7bf5aec997ac0e897949d9b9e41a28ddebbeaba69753fee7d2de75e518091518185085fcd1f6ada94b7231097b2e
…ignTransaction 99e88a3 rpc: Remove dependency on interfaces::Chain in SignTransaction (Antoine Riard) Pull request description: Assuming wallet RPCs and node RPCs will go into different processes, signrawtransactionwithkey doesn't need to access Coins via interfaces::Chain, it may use directly utility in node/coins.cpp Obviously will need rebase after bitcoin#15638 Tree-SHA512: 42ee8fcbcd38643bbd82210db6f68249bed5ee036a4c930a1db534d0469a133e287b8869c977bf0cc79a7296dde04f72adb74d24e1cd20f4a280f4c2b7fceb74
…amples 71fd628 Add example 2nd arg to signrawtransactionwithkey (Chris Moore) Pull request description: The RPC examples for signrawtransactionwithkey are missing the 2nd parameter. Before this change the help text showed: Examples: > bitcoin-cli signrawtransactionwithkey "myhex" > curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "signrawtransactionwithkey", "params": ["myhex"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/ With the change, it shows: Examples: > bitcoin-cli signrawtransactionwithkey "myhex" "[\"key1\",\"key2\"]" > curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "signrawtransactionwithkey", "params": ["myhex", "[\"key1\",\"key2\"]"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/ ACKs for commit 71fd62: Tree-SHA512: dadf6bf0ba64ac356b7b8f9ed4d483384b70080ac4b1664b27a2e72b97f25d7266f3dae89fbeade73c1bae802b5bae7b84d596c93a9ae9c748851ae35758d9a6
…ht excl genesis fab0c82 rpc: Clarify that block count means height excl genesis (MarcoFalke) Pull request description: There is a common misconception that the block count returned by the blockchain rpcs includes the genesis block. See for example the discussion in bitcoin#16292 (comment). However, it really returns the height, which is `0` for the genesis block. So clarify that and also remove the misleading "longest blockchain" comment. Finally, fix the wallet test that incorrectly used this rpc. ACKs for top commit: instagibbs: utACK bitcoin@fab0c82 promag: ACK fab0c82, sorry for the misconception. Tree-SHA512: 0d087cbb628d3866352bca6420402f392e6a997e579941701a408a7fca355d84645045661f39b022e4479cc07f85a6cddaa9095b6fd9911b245692482420a5e4
PastaPastaPasta
left a comment
There was a problem hiding this comment.
utACK for merging via merge commit
nit: please name 16325 as not being partial (all substance was done), but that's not a blocker imo
|
Sure, will do
…On Tue, 4 Jan 2022, 13:31 PastaPastaPasta, ***@***.***> wrote:
***@***.**** approved this pull request.
utACK for merging via merge commit
nit: please name 16325 as not being partial (all substance was done), but
that's not a blocker imo
—
Reply to this email directly, view it on GitHub
<#4613 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR5IIWRQWHMQEGIQANGXJDUUKSOHANCNFSM5JR6AYHQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hello @UdjinM6 please re approve , approval got dismissed after force push after rebase |
No description provided.