[thegraph][bug] deposit id/tx wrong about aave-protocol

[kyzia551]

Hello @sakulstra !

Thank you very much for research. I will remove this "d" letter soon.

The issue is related to that I used a common interface for the most part of the pool operations, which is not allowing to use same id for different entities compatible with this interface

Is it matter for you to have direct access to pool interactions by txHash? Because the main problem is that it could be more than 1 deposit in the same tx, and I'm thinking about how to make this id unique and easily accessable for end users. Is the idea with numbers after txHash like
id: txHash + 0..9 will fit for you?

[sakulstra]

@kyzia551 I just noticed it when trying to link the deposit transactions on aavewatch.now.sh to the corresponding etherscan transaction.

While this would work for me, i'd prefer having id as sth unique (I don't really care to much how it is constructed- but i guess 0..9 would fall short when more than 9 deposits are done in a single transaction?), but also having the tx as part of the payload.

id: ID! # some unique id
tx: ID! # not necessarily unique tx hash