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

Allow counterfactual contract deployment. #13

Closed
Georgi87 opened this issue Feb 4, 2020 · 1 comment
Closed

Allow counterfactual contract deployment. #13

Georgi87 opened this issue Feb 4, 2020 · 1 comment
Labels
contracts This issue is related to contract changes

Comments

@Georgi87
Copy link

Georgi87 commented Feb 4, 2020

Use case:
To allow non-web3 wallets (no in-app browser or wallet connect) to participate in Dapps, it is required to allow all interaction including approvals of tokens without asking the user to send transactions. In addition, this change also requires the user to sign only one transaction, the approval transaction for the proxy contract can be cut. This functionality can be implemented by asking the user to send tokens to a counterfactual contract address and deploying the contract with a relayer service, which can be reimbursed from the contract account (like we do it for the Safe app).

@cag cag mentioned this issue Feb 25, 2020
@cag cag added the contracts This issue is related to contract changes label Apr 30, 2020
@cag cag mentioned this issue May 1, 2020
3 tasks
@rmeissner
Copy link
Member

will be handled in #67

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contracts This issue is related to contract changes
Projects
None yet
Development

No branches or pull requests

3 participants