Skip to content

Feature request: allow Safe Apps to take msg.value from Safe signer instead of Safe itself #648

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

Open
PaulRBerg opened this issue Apr 4, 2025 · 0 comments

Comments

@PaulRBerg
Copy link
Contributor

Problem

There are apps like Sablier who monetize by charging ETH fees via msg.value.

By default, a Safe tx tries to take msg.value from the Safe address itself, not from the signer who executes the tx.

The problem is that few Safes keep ETH in their multisigs, which makes monetization difficult (our assumption was that the account paying the gas for the tx would be the same account who is debited via msg.value, but this is not true for Safes).

As a workaround, we ended up adding this warning in the Sablier UI:

Solution

Allow Safe Apps to take msg.value from Safe signer instead of the Safe itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant