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
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: