-
Notifications
You must be signed in to change notification settings - Fork 213
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
No event created for tracked address in 2-block reorg #409
Comments
I ran with v2.3.55 |
This is by design, there is no event in case of reorg. However, querying the API or balance should reflect that the transaction isn't confirmed anymore. I advice to just wait every block and check the confirmation count of TX at each block until you reach a good enough level for your situation. |
But why does it create an event in the case of a 1-block reorg, then? |
I will take a look tomorrow. I guess it's because 1 block reorg send the transaction back in mempool. Not 2 block reorg. I'll check. |
I tried to reproduce but it doesn't work for me. I'm not sure why you are seeing this, but my guess is that after the reorg of 1 block, the transaction goes back to mempool and get sent again to NBX. |
I haven't put any more effort into nailing this down, as it's not a probable scenario, and we can semi-manually clean up any mess that it causes. |
fix in v2.5.1 |
v2.5.1 doesn't fix this issue. |
Please reopen this issue since it's not a duplicate of #461 |
I'm running NBX on a regtest node. If the current tip is at height 103 and
invalidateblock
for height 102I expect to get a
newtransaction
event that saysconfirmations: 0
innbxv1_evts
.I get no such event.
But if the current tip is 102, and the tx is at 102, and I
invalidateblock
102, then I do get anewtransaction
event that saysconfirmations: 0
.To me this seems like a bug, but I'm also open to the possibility that I'm making a stupid mistake.
Details
2 blocks reorg
Reorg 2 block deep (
invalidateblock
102) with tx at block 102.nbxv1_evts
:From debug.log (wallet
user
is the wallet containing the tracked address).1 block reorg (exact same test otherwise)
Reorg 1 block deep (
invalidateblock
102) with tx at block 102nbxv1_evts
:From debug.log
The text was updated successfully, but these errors were encountered: