diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-03-13 17:58:52 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-03-13 18:00:06 +0100 |
| commit | 702e8b70bd870f506ce8157e58b77cb7d0a0f98d (patch) | |
| tree | 089aad138eced3caaf758d325214c28d1b83cc35 /doc/build-windows.md | |
| parent | 0f0229d0c36310eea329716fbc81541c7c3a62b1 (diff) | |
| parent | fac70134a9e3a1fc8e491aecb3c36d0184ba7b82 (diff) | |
Merge #11872: [rpc] createrawtransaction: Accept sorted outputs
fac70134a rpc: Update createrawtransaction examples (MarcoFalke)
fa06dfce0 [rpc] createrawtransaction: Accept sorted outputs (MarcoFalke)
8acd25d85 rpc: Allow typeAny in RPCTypeCheck (MarcoFalke)
Pull request description:
The second parameter of the `createrawtransaction` is a dictionary of the outputs. This comes with at least two drawbacks:
* In case of duplicate keys, either of them might silently disappear, with no user feedback at all. A user needs to make other mistakes, but this could eventually lead to abnormal tx fees.
* A dictionary does not guarantee that keys are sorted. Again, a user needs to keep this in mind, as it could eventually lead to excessive tx fees.
Even though my scenario of loss-of-funds is unlikely to happen, I see it as a inconvenience that should be fixed.
Tree-SHA512: cd562f34f7f9f79c7d3433805971325c388c2035611be283980f4049066a622df4f0afdc11d7ac96662260ec0115147cb65e1ab5268f5a1b063242f3fe425f77
Diffstat (limited to 'doc/build-windows.md')
0 files changed, 0 insertions, 0 deletions