mirror of
https://github.com/dashpay/dash.git
synced 2024-12-26 20:42:59 +01:00
cd490905be
ce07638doc: Add comment to use ValueFromAmount/AmountFromValue for JSON, not utilmoneystr (Wladimir J. van der Laan)ec05c50rpc: Use ValueFromAmount instead of FormatMoney in TxToUniv (Wladimir J. van der Laan)46347adrpc: Move ValueFromAmount to core_write (Wladimir J. van der Laan)dac3782doc: Correct AmountFromValue/ValueFromAmount names (Wladimir J. van der Laan) Pull request description: With this, the amounts returned in `decoderawtransaction` will be padded to 8 digits like anywhere else in the API. This is accomplished by using `ValueFromAmount` in `TxToUniv`, instead of `FormatMoney` which it currently (mistakingly) uses. The `FormatMoney` function is only for debugging/logging use! To avoid dependency issues, `ValueFromAmount` is moved to `core_write.cpp`, where it also fits better. I don't move `AmountFromValue` to `core_read.cpp` at the same time, as this would have more impact due to the RPCError dependency there. (n.b.: large number of changed files is solely due to the util_tests JSONs needing update) Tree-SHA512: 10fc2d27d33a77dbcb57aa7eccd4f53110c05d38eb7df6d40f10f14c08fad4274472e93af75aa59fe68ad0720fdf0930f0108124abef518e0dd162b3d2b2b292
22 lines
466 B
JSON
22 lines
466 B
JSON
{
|
|
"txid": "0481afb29931341d0d7861d8a2f6f26456fa042abf54a23e96440ed7946e0715",
|
|
"version": 2,
|
|
"size": 19,
|
|
"locktime": 0,
|
|
"vin": [
|
|
],
|
|
"vout": [
|
|
{
|
|
"value": 0.00000000,
|
|
"valueSat": 0,
|
|
"n": 0,
|
|
"scriptPubKey": {
|
|
"asm": "",
|
|
"hex": "",
|
|
"type": "nonstandard"
|
|
}
|
|
}
|
|
],
|
|
"hex": "02000000000100000000000000000000000000"
|
|
}
|