-
Notifications
You must be signed in to change notification settings - Fork 275
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
Bulk Token Assignment/Burning #585
Comments
This is a problem we have experienced. We have an existing token with several thousand holders. Since we can't use the existing token stakes to vote. It's not feasible to assign 1000's of addresses to the token manager. Therefore a useful solution for us would be some form of bulk upload of addresses to assign tokens to. Such as feeding the token manager a CSV of addresses I could download from Etherscan. |
Bump! Is there any progress on this one :-D? |
No; in the best case this will require contract upgrades which will not happen until at least Q2 2020. |
I did this script using the aragon-cli toolkit: https://github.com/sembrestels/aragon-toolkit-examples/tree/master/examples/mintAndBurn I think it is easy to embed this code in an app that do bulk payments, assignments, and token burnings. Is there interest in integrating it in the token manager / finance apps? Does it has sense to do a separate app for bulk operations? |
Just wow!Your are crushing it Sem. I'll pm you to sync about improvements on the Toolkit 🙌 |
No; encoding multiple actions in an evmscript should be covered by #363 (or further derivatives). |
This requires either a contract upgrade or #363. We will evaluate further contract changes in aragon/aragon-apps#1101 and for now, close this in favor of #363. |
Note: this has been closed to be tracked in the "wishlist for future upgrades".
Is your feature request related to a problem? Please describe.
I'm currently using Aragon and find that I often need to update multiple token balances at once. Currently this means signing each transaction individually, (and if the action requires a vote each voter also needs to sign a transaction to approve each change). This is both cumbersome and incredibly costly. It should be possible to update multiple token balances in a single operation.
Describe the solution you'd like
I want to be able to efficiently perform a mint or burn operation that updates the balances of multiple accounts in a single atomic operation.
Describe alternatives you've considered
#363 describes a possible solution that would be probably applicable (though not sure how much more efficient it makes things). In this require queuing up individual actions and then submitting them all at once, this would save a lot of effort as you would only need to sign and send a single transaction (and voters would only need to approve or reject a single action).
It still may not be the ideal solution for this specific issue, as it might be useful to provide and interface that allows you to update a list/array of balances and submit that rather going to mint or burn for each balance individually.
Additional context
I think for many usecases this problem is an opportunity to drastically improve scalability/cost simply by minimizing the number of transactions that need to occur.
The text was updated successfully, but these errors were encountered: