Open m4ktub opened 4 years ago
Previously (for example, when #532 was reported) the txDetails would count the OP_RETURN output as any other output which meant it would set its value to 0 in tokenInfo.sendOutputs. For example
txDetails
OP_RETURN
tokenInfo.sendOutputs
{ "tokenInfo": { "versionType":1, "transactionType":"SEND", "tokenIdHex":"49be89bbbe018bcfaebcb41cac8340bc555f022b47b922599e510b143603f4b6", "sendOutputs": [ "0", "1" ] } }
But the API changed in a breaking way and now OP_RETURN is not excluded. For the same example shown before it not returns:
{ "tokenInfo": { "versionType":1, "transactionType":"SEND", "tokenIdHex":"49be89bbbe018bcfaebcb41cac8340bc555f022b47b922599e510b143603f4b6", "sendOutputs": [ "1" ] } }
This means that the index of the value and the index of the vout no longer match.
Previously (for example, when #532 was reported) the
txDetails
would count theOP_RETURN
output as any other output which meant it would set its value to 0 intokenInfo.sendOutputs
. For exampleBut the API changed in a breaking way and now OP_RETURN is not excluded. For the same example shown before it not returns:
This means that the index of the value and the index of the vout no longer match.