[feature]: add account parameter to Transaction in SubscribeTransactions

[izako666]

Is your feature request related to a problem? Please describe.
For my specific use case, I have a main tracking node with children nodes included as accounts to the main node. These children nodes are for each user and as such scale to the amount of users using my service. In order to track and update my database with transaction information, at this current point in time I have to subscribe to every single node for every user. A setup like that can quickly break when the amount of users becomes too big to manage.

Describe the solution you'd like
I would like for the account name to be included with each incoming transaction data model. I know that you can filter for account name in SubscribeTransactions when you make the request, so it should be theoretically possible to include the account name with each transaction.

Describe alternatives you've considered
I have also tried attributing a transaction to a user through the addresses used, by keeping a list of all addresses the user currently owns, however this also scales very poorly, as I have to have loaded every address for every user along with keeping track of any new addresses being created.

Additional context
I would also like to add that I am a bit in-experienced with all things crypto, so there may be an easier solution I am overlooking, however I'd like to open up this issue as a discussion, to see where I could go from here.

[weltitob]

@izako666, @guggero this is an important issue this can be used as a LSP to track the onchain transactions of accounts of mutiple users without hassle only by using one node - is there any article or some other option how this can be archived?

[guggero]

Hmm, it looks like the account name in SubscribeTransactions and even GetTransactions isn't used at all, so it doesn't have any effect... So to achieve this the btcwallet would need to be refactored quite a bit.