There is no way to identify the caller of Multisend and Lockbox contracts.
Impact
Why is it important? Who requested it? Who does it impact? What data do we have to suggest this is a problem? Is there specific timelines that increase urgency?
This is a crucial piece of analytics of volume attribution
Proposed Solution
Pull the data from subgraphs and identify the caller.
Acceptance Criteria
From an end user perspective, the below criteria must be met to consider this done:
For each of the Connext deployed contracts it is clearly identifiable:
Wallet address of the origin user, caller of the Connext contract, destination address
linear[bot]
commented
3 months ago
Problem
There is no way to identify the caller of Multisend and Lockbox contracts.
Impact
Why is it important? Who requested it? Who does it impact? What data do we have to suggest this is a problem? Is there specific timelines that increase urgency? This is a crucial piece of analytics of volume attribution
Proposed Solution
Pull the data from subgraphs and identify the caller.
Acceptance Criteria
From an end user perspective, the below criteria must be met to consider this done: For each of the Connext deployed contracts it is clearly identifiable: Wallet address of the origin user, caller of the Connext contract, destination address