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
This solution isn't fully developed as it only works for a single chain, making it cumbersome for users if partners use different chains. Deploying a SAFE with the same address across multiple chains is challenging.
However, by adding a special feature for Gnosis Chain, which sponsors up to five transactions per hour, we can enhance the user experience by eliminating gas fee concerns.
This approach addresses our issues related to creating a faucet.
This may require generating a private signing key in browser, proposal here. Once the signing key has been added to the user's SAFE as an authorized signer, it should be able to prompt the SAFE that new transactions are waiting to be approved. This would work well on mobile due to the push notifications SAFE produces when a signature request occurs.
As for desktop I am not 100% sure.
The best part about this is that the gas fee will be sponsored, so the in browser signing key never has to hold any value.
The text was updated successfully, but these errors were encountered:
This solution isn't fully developed as it only works for a single chain, making it cumbersome for users if partners use different chains. Deploying a SAFE with the same address across multiple chains is challenging.
However, by adding a special feature for Gnosis Chain, which sponsors up to five transactions per hour, we can enhance the user experience by eliminating gas fee concerns.
This approach addresses our issues related to creating a faucet.
More about gas fee sponsoring
An idea for seamless UX:
This may require generating a private signing key in browser, proposal here. Once the signing key has been added to the user's SAFE as an authorized signer, it should be able to prompt the SAFE that new transactions are waiting to be approved. This would work well on mobile due to the push notifications SAFE produces when a signature request occurs.
As for desktop I am not 100% sure.
The best part about this is that the gas fee will be sponsored, so the in browser signing key never has to hold any value.
The text was updated successfully, but these errors were encountered: