-
Notifications
You must be signed in to change notification settings - Fork 19
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
Automatic Transfer #6
Comments
@gentlementlegen something to keep in mind as you work on permit generation: the ability for plugin developers to be able to easily capture value. Like a percentage/flat rate transaction fee. Ideally the plugin developer should have the value automatically transferred to their wallet, but we may be able to prototype this with permits. |
/start |
Tips:
|
/stop |
+ You have been unassigned from the task |
/start |
@surafeldev the deadline is at Thu, Oct 3, 12:12 PM UTC |
@surafeldev, this task has been idle for a while. Please provide an update. |
…t-config feat: updated eslint to use flat-config file
Passed the deadline and no activity is detected, removing assignees: @surafeldev. |
The permit generation plugin should also optionally be able to automatically invoke a transfer to the beneficiaries.
This introduces additional complexities because it must be able to estimate the gas fee of the transaction (given that we must support multiple EVM networks, with varying levels of activity, it is not viable to hard code this.)
In an org/repo config we can have a property related to payments
transfer: true
It should also allow for the kernel operator (@ubiquity) to take a fee1. This fee should be configured elsewhere, perhaps in Cloudflare Worker Secrets (partner projects should not be able to change this.) Any fees that we take should be direct transfers of Ubiquity Dollars to
ubq.eth
.Footnotes
This means we have to start thinking about how to capture value from payments moving around in our system. I think that we need to make a superior developer experience with our SDK and permit requests, so that plugin developers can easily capture value from the transactions their plugins are helping with. ↩
The text was updated successfully, but these errors were encountered: