You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this is non-trivial for Connect, because it requires app-level information (and even then it may be difficult due to the lack of explicit information in events or other details).
Ideally, if you had an organization requiring a multi-step transaction path to execute an action, for example:
Approval (smaller group)
Delay (time constraint to notify potential voters)
Voting (large group)
It would be ideal if a user could establish a link between an action going through the different steps, for example:
Approval#4 created Delay#5
Delay#5 created Vote#2
Vote#2 can be traced all the way back to Approval#4 (and any other intermediate steps as necessary)
This would be useful for building UI that explains the path an action took, for example, to show all the steps taken (and to be taken) in one "proposal" detail view.
(If an action was at the middle Delay step, it would only be able to tell users that a potential vote may be created; see larger description)
The only way I know how to do this now is by inspecting the transaction that created a particular action (e.g. Vote#2). You can eventually follow the logs to know that a particular Dispute#5 created the vote, but this is both slow and requires a lot of additional context. It would be much, much better if we could find a way to do this through a subgraph or another approach.
The text was updated successfully, but these errors were encountered:
I think this is non-trivial for Connect, because it requires app-level information (and even then it may be difficult due to the lack of explicit information in events or other details).
Ideally, if you had an organization requiring a multi-step transaction path to execute an action, for example:
It would be ideal if a user could establish a link between an action going through the different steps, for example:
Approval#4
createdDelay#5
Delay#5
createdVote#2
Vote#2
can be traced all the way back toApproval#4
(and any other intermediate steps as necessary)This would be useful for building UI that explains the path an action took, for example, to show all the steps taken (and to be taken) in one "proposal" detail view.
(If an action was at the middle Delay step, it would only be able to tell users that a potential vote may be created; see larger description)
The only way I know how to do this now is by inspecting the transaction that created a particular action (e.g.
Vote#2
). You can eventually follow the logs to know that a particularDispute#5
created the vote, but this is both slow and requires a lot of additional context. It would be much, much better if we could find a way to do this through a subgraph or another approach.The text was updated successfully, but these errors were encountered: