We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Figure out how to add a method to the sdk that will let users easily add their campaign to efxtaskproxy.
Either it is a checkbox in the campaign creation form, or programmatically in the sdk.
Probably an action needs to be created to adjust the permissions on eosio.
An alternative is to let the owner of the campaign transfer their ownership of the campaign to Effect Network's efxtaskproxy.
The problem here is that they will not be able to edit their campaigns anymore.
This feature needs to be thought out further to make sure that it is a solid process that users and devs can rely on.
The text was updated successfully, but these errors were encountered:
The preferred way to achieve this is by changing the campaign owner, which is covered here: #106
To make this feature complete we will need to update the task proxy to remember the original campaign owner and allow it to be changed back.
Sorry, something went wrong.
This workflow is obsolete in V2
No branches or pull requests
Feature
Figure out how to add a method to the sdk that will let users easily add their campaign to efxtaskproxy.
Either it is a checkbox in the campaign creation form, or programmatically in the sdk.
Probably an action needs to be created to adjust the permissions on eosio.
An alternative is to let the owner of the campaign transfer their ownership of the campaign to Effect Network's efxtaskproxy.
The problem here is that they will not be able to edit their campaigns anymore.
This feature needs to be thought out further to make sure that it is a solid process that users and devs can rely on.
Description
Steps
The text was updated successfully, but these errors were encountered: