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
After InstantX confirms on the network, it's hard to tell if it succeeded via the API. Currently the best way is to use gettransaction {txid}, then grab the "confirmations" which also includes IX confirmations .
I propose adding a separate command, which would tell you if a transaction was safe.
getixstatus {txid} -> returns "locked", "unknown", "unconfirmed" or "failure"
Also, adding the "ixstatus" field to gettransaction, which would make understanding the output a lot easier.
Merchants running the full daemon could then easily utilize IX when receiving funds.
The text was updated successfully, but these errors were encountered:
Well, we never implemented anything like getixstatus but yes, all wallet tx-related RPCs should have instantlock (bool) field to indicate the IS status now. So the issue is half-fixed but I'm not sure if we need smth like getixstatus at all, probably not.
After InstantX confirms on the network, it's hard to tell if it succeeded via the API. Currently the best way is to use gettransaction {txid}, then grab the "confirmations" which also includes IX confirmations .
https://github.com/dashpay/dash/blob/master/src/rpcwallet.cpp#L1597
I propose adding a separate command, which would tell you if a transaction was safe.
getixstatus {txid} -> returns "locked", "unknown", "unconfirmed" or "failure"
Also, adding the "ixstatus" field to gettransaction, which would make understanding the output a lot easier.
Merchants running the full daemon could then easily utilize IX when receiving funds.
The text was updated successfully, but these errors were encountered: