Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

electrs: UTXO included in unconfirmed transaction inputs are returned in the unspent #66

Open
ahonn opened this issue Apr 8, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ahonn
Copy link
Contributor

ahonn commented Apr 8, 2024

How to reproduce

  • btc_address has 2 UTXOs: UTXO#A and UTXO#B
  • sent a transaction that uses UTXO#A as input.
  • Before tx is confirmed, /bitcoin/v1/address/{address}/unspent will still return UTXO#A.

Actual

Return UTXO#A and UTXO#B before tx is confirmed.

Expected

Return UTXO#B only before tx is confirmed.

Note

We can use the API provided by blockstream/electrs for comparison.
eg. https://blockstream.info/testnet/api/address/tb1qm4eyx777203zmajlawz958wn27z08envm2jelm/utxo

I reckon this might be due to differences in the config between our deployed electrs and the one deployed by blockstream. We need to dig deeper to confirm.

@ahonn ahonn added the bug Something isn't working label Apr 8, 2024
@ahonn ahonn changed the title UTXO included in unconfirmed transaction inputs are still returned in the spent api UTXO included in unconfirmed transaction inputs are returned in the unspent Apr 8, 2024
@Flouse Flouse changed the title UTXO included in unconfirmed transaction inputs are returned in the unspent electrs: UTXO included in unconfirmed transaction inputs are returned in the unspent Apr 8, 2024
@Flouse
Copy link
Contributor

Flouse commented May 7, 2024

I reckon this might be due to differences in the config between our deployed electrs and the one deployed by blockstream. We need to dig deeper to confirm.

Maybe the reason is the different pending transaction set in different electrs + btc-node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants