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
Hitting https://rest.bitbox.earth/v1/address/utxo/ with a stringified array of cashaddress formatted addresses frequently yields different results. This is true if you hit the server directly and also if you use the Bitbox-cliBITBOX.Address.utxo() method.
If I remember correctly, this endpoint is relayed from Bitcoin.com . If that's true, then the problem might actually be their Insight node. Strangely enough, #17 looks like it might also be a problem with Bitcoin.com . I've commented on that issue as well.
EDIT: I tried hitting the endpoint one time for each address and it didn't fix the problem. Same symptoms exactly. I'm certain this is a problem with the Bitcoin.com Insight API library.
The text was updated successfully, but these errors were encountered:
Hitting
https://rest.bitbox.earth/v1/address/utxo/
with a stringified array of cashaddress formatted addresses frequently yields different results. This is true if you hit the server directly and also if you use theBitbox-cli
BITBOX.Address.utxo()
method.If I remember correctly, this endpoint is relayed from Bitcoin.com . If that's true, then the problem might actually be their Insight node. Strangely enough, #17 looks like it might also be a problem with Bitcoin.com . I've commented on that issue as well.
Here's a script that demonstrates my problem: https://gist.github.com/alwaysAn0n/433616933f2a0dbefe03c71650caa38a
EDIT: I tried hitting the endpoint one time for each address and it didn't fix the problem. Same symptoms exactly. I'm certain this is a problem with the Bitcoin.com Insight API library.
The text was updated successfully, but these errors were encountered: