dApp shows wrong TX value if transaction change address is different

[lenilsonjr]

Operation System

MacOS

Expected Behavior

If I receive a transaction and the change address for that transaction is different than the sender, the dApp should still ignore change value when displaying the tx in my activity.

Current Behavior

the dApp will recognize the whole value of the tx as an activity for my address.

Possible Solution (Not obligatory)

Filter tx.ins for the logged in address, so we can always ignore inputs and outputs not related to our address, when displaying wallet activity

[piggydoughnut]

I will move this to nspv-js as this is definitely a transaction parsting problem

[piggydoughnut]

@lenilsonjr I think I fixed that with the last issue. See PR #22

I am taking in consideration the address of the logged in user (passing address property) when parsing transaction. If I cannot find any address that is receiving change, I check if my address is in the list of addresses that are vouts of this transaction and if it is, I take the value from vout that is going to my address as transaction value.