sha-265
sha-265
No. Not on-chain txs at all, I'm talking about regular LN txs.
> So can you please try if the new release would fix it? I tried. Unfortunately the problem still exists.
> Can you reproduce this issue? Nope.
you are too fast 😵💫 anyway, this is probably a good opportunity to fix `getTransactions()` that uses wrong api method (`listfunds` which return the wallet utxos, and not transactions history),...
> > anyway, this is probably a good opportunity to fix `getTransactions()` that uses wrong api method (`listfunds` which return the wallet utxos, and not transactions history), as i did...
> > i don't see this tags (at least under `wallet` account), but there is a `journal_entry` tag that should be filtered out maybe. > > Yeah, that's the problem,...
> > i'm not sure these events are relevant if you want only the on-chain transactions. > > I think they are relevant because channel opens and closes are chain...
> > but i think in terms of performance query without account parameter, would be much more heavy as it returns all the non on-chain events > > I agree....
> I don't expect to see channel open / close transactions i agree, and it's also solve the potential performance issue, as you can request only `wallet` account events, and...
i don't understand how tons of irrelevant events solving this, but at least you should get the same data only once and not three different times.