Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Transaction meta data #331

Open
tschubotz opened this issue Aug 11, 2021 · 2 comments
Open

Feature request: Transaction meta data #331

tschubotz opened this issue Aug 11, 2021 · 2 comments
Labels
future Features for next major contract version

Comments

@tschubotz
Copy link
Member

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.

@mmv08
Copy link
Member

mmv08 commented Nov 1, 2021

Maybe this can be useful: https://github.com/0xsequence/sstore2

@Slyracoon23
Copy link

I am actually interested in this feature as well. Especially for DAO that use Gnosis-safe for distributing funds.

fdarian pushed a commit to fdarian/safe-contracts that referenced this issue Jan 14, 2024
@rmeissner rmeissner added the future Features for next major contract version label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future Features for next major contract version
Projects
None yet
Development

No branches or pull requests

4 participants