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
The Get BTC UTXO api endpoint (/v1/indexer/address/{address}/utxo-data) is returning utxos with runes on them in testnet.
The docs for this endpoint simply state "Get non inscription UTXO list by address", so it doesn't specifically mention runes, however, based on its behaviour on mainnet, I am led to believe that this endpoint also does not give rune UTXO's. If this is the case, it is not behaving as expected on testnet.
This is quite concerning to me. If it is not working on testnet, it makes me question if this could also happen on mainnet. I assume this endpoint is being used by dapps to determine which UTXO's are safe to spend, so if this endpoint is returning incorrect data, it could lead to people losing runes.
In addition to the issue with testnet, it is also an issue that the docs are not specific about this endpoint. Since they do not mention runes, it unclear if it should be returning these UTXO's. Please add details indicating if this endpoint does or does not return UTXO's with runes in them. My assumption is that this endpoint returns UTXO's that are 'safe to spend', but this is not clear from the description. It should be made clear that the UTXO's returned from this endpoint are safe to spend, so there is no confusion for future developers.
Here is an example showing rune UTXO's being returned on testnet:
Make a request to this endpoint: https://open-api-testnet.unisat.io/v1/indexer/runes/utxo/815762e3fcad0ce3d7492df0ddd47437c39e4da73f5d7cf127ee176767197c40/0/balance
It returns this response, indicating this UTXO has runes on it:
Now, make a request to this endpoint: https://open-api-testnet.unisat.io/v1/indexer/address/tb1pq292yrq67pkzssy2nt9hxzl7dcst79wj0ukr2z94c02v2fna3prqpylg44/utxo-data
It returns this response:
I have tried adding the confirmed=true query param, however this does not change the response. I am not surprised either. The implication is that the confirmed parameter should filter out UTXO's that have not been confirmed (i.e. mined). However, all UTXO's in the response I shared are confirmed, so this parameter should not have any effect. I would not expect the confirmed query param to have any impact on runes UTXO's, and if it did that would be very counter intuitive. I understand that the API is not aware of runes/inscriptions on unconfirmed UTXO's, but that is not the issue here, as all UTXO's are confirmed.
The Get BTC UTXO api endpoint (
/v1/indexer/address/{address}/utxo-data
) is returning utxos with runes on them in testnet.The docs for this endpoint simply state "Get non inscription UTXO list by address", so it doesn't specifically mention runes, however, based on its behaviour on mainnet, I am led to believe that this endpoint also does not give rune UTXO's. If this is the case, it is not behaving as expected on testnet.
This is quite concerning to me. If it is not working on testnet, it makes me question if this could also happen on mainnet. I assume this endpoint is being used by dapps to determine which UTXO's are safe to spend, so if this endpoint is returning incorrect data, it could lead to people losing runes.
In addition to the issue with testnet, it is also an issue that the docs are not specific about this endpoint. Since they do not mention runes, it unclear if it should be returning these UTXO's. Please add details indicating if this endpoint does or does not return UTXO's with runes in them. My assumption is that this endpoint returns UTXO's that are 'safe to spend', but this is not clear from the description. It should be made clear that the UTXO's returned from this endpoint are safe to spend, so there is no confusion for future developers.
Here is an example showing rune UTXO's being returned on testnet:
Make a request to this endpoint:
https://open-api-testnet.unisat.io/v1/indexer/runes/utxo/815762e3fcad0ce3d7492df0ddd47437c39e4da73f5d7cf127ee176767197c40/0/balance
It returns this response, indicating this UTXO has runes on it:
Now, make a request to this endpoint:
https://open-api-testnet.unisat.io/v1/indexer/address/tb1pq292yrq67pkzssy2nt9hxzl7dcst79wj0ukr2z94c02v2fna3prqpylg44/utxo-data
It returns this response:
The final UTXO is
815762e3fcad0ce3d7492df0ddd47437c39e4da73f5d7cf127ee176767197c40:0
. i.e. the same UTXO is the first request that has runes on it.The text was updated successfully, but these errors were encountered: