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
Transaction meta data: I would like to be a to (optionally) provide meta data when calling execTransaction.
Why?
Safe transactions are triggered via different interfaces. Also the officiel safe-react interface has Safe apps. The information on which txs was triggered via which Safe app is currently stored exclusively in our backend. This is not great for analytics since we can't easily match it with on-chain data from dune.
Proposed solution
Add an optional field to execTransaction where arbitrary data could be provided. This data should not be used at all for tx execution. It's sole purpose is for this info to be stored on chain via the call trace.
Alternatives
Additionally trigger an event with this info. I currently don't think this is necessary.
The text was updated successfully, but these errors were encountered:
Context / issue
Transaction meta data: I would like to be a to (optionally) provide meta data when calling
execTransaction
.Why?
Safe transactions are triggered via different interfaces. Also the officiel safe-react interface has Safe apps. The information on which txs was triggered via which Safe app is currently stored exclusively in our backend. This is not great for analytics since we can't easily match it with on-chain data from dune.
Proposed solution
Add an optional field to
execTransaction
where arbitrary data could be provided. This data should not be used at all for tx execution. It's sole purpose is for this info to be stored on chain via the call trace.Alternatives
Additionally trigger an event with this info. I currently don't think this is necessary.
The text was updated successfully, but these errors were encountered: