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

subscribetransactions fires duplicated event when a transaction is received #2267

Open
joaodealmeida opened this Issue Dec 4, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@joaodealmeida

joaodealmeida commented Dec 4, 2018

Background

subscribetransactions is firing 2 events per tx received. Whenever I receive a transaction, lnd fires 2 events containing the same payload.

The transaction gets notified independent from the block notification once it’s confirmed and it’s also notified when processing the block notification containing the transaction.

Your environment

  • version of lnd - 0.5.1-beta commit=v0.5.1-beta-dirty
  • which operating system (uname -a on *Nix) - Linux ip-172-31-4-119 4.4.0-1060-aws #69-Ubuntu SMP Sun May 20 13:42:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  • version of btcd, bitcoind, or other backend - bitcoind

Steps to reproduce

  • Listen suscribetransactions
  • Generate an address
  • Send btc to that address

Expected behaviour

An event should be fired only when the transaction gets notified independent from the block notification once it’s confirmed.

Actual behaviour

An event is also fired when processing the block notification containing the transaction.

@joaodealmeida joaodealmeida changed the title from subscribetransactions fires 2 duplicated event on tx received to subscribetransactions fires duplicated event when a transaction is received Dec 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment