You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since getaddressuxtos is not reliable for realtime information (because it is not instantsend-aware), 'getaddressdeltas' must be used in conjunction with 'getaddressmempool' in order to get the correct uxtos.
However, neither 'getaddressdeltas' nor 'getaddressmempool' include script, which means that in order to use as a utxo for creating a transaction, the pkh has to be reproduced, which requires more wallet machinery in place, which leads to code that's more cumbersome when building a wallet.
Likewise, the deltasmempool fail to specify outputIndex vs inputIndex. This is workable since a negative satoshis value indicates inputIndex, otherwise it's outputIndex, but it would be nice if it were consistent to the delta type.
Related to dashpay/docs-core#40
Since
getaddressuxtos
is not reliable for realtime information (because it is notinstantsend
-aware), 'getaddressdeltas' must be used in conjunction with 'getaddressmempool' in order to get the correctuxtos
.However, neither 'getaddressdeltas' nor 'getaddressmempool' include
script
, which means that in order to use as a utxo for creating a transaction, thepkh
has to be reproduced, which requires more wallet machinery in place, which leads to code that's more cumbersome when building a wallet.Likewise, the
deltas
mempool
fail to specifyoutputIndex
vsinputIndex
. This is workable since a negativesatoshis
value indicatesinputIndex
, otherwise it'soutputIndex
, but it would be nice if it were consistent to the delta type.Example
getaddressuxtos
https://trpc.digitalcash.dev/#?method=getaddressutxos¶ms=[{"addresses":["yQzps4ubfPzVdPUXNYAG9B6BvED1Jttaa8"]}]&submit
Example
getaddressdeltas
Example
getaddressmempool
I can't link to it because it's ephemeral data, but I believe it's exactly the same object as
getaddressdeltas
.The text was updated successfully, but these errors were encountered: