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

deploying a new organization takes a lot of work #47

Closed
jellegerbrandy opened this issue Jul 15, 2017 · 2 comments
Closed

deploying a new organization takes a lot of work #47

jellegerbrandy opened this issue Jul 15, 2017 · 2 comments

Comments

@jellegerbrandy
Copy link
Contributor

One of the main points of the genesisscheme is to simplify the deployment into as few transactions as possible. This is working out not so good.

At the moment of writing (commit 64c1554) the deployment procedure of a new organization that uses only already existing schemes takes 8 different transactions, plus you need to have tokens to pay for registering your organization with the schemes (at the moment 3, possibly different from each other).

The relevant code is here: https://github.com/daostack/daostack/blob/64c1554a003512c1cfc436040acc0bb114a13c8b/lib/organization.js#L24

@jellegerbrandy
Copy link
Contributor Author

(my personal opinion remains that this is a UX problem that should not be solved onchain. I.e. it is fine to have many transcations, we just need to hide the pain from the user by (1) checking all preconditions carefully before doing anything and (2) hide the fact that the transactions are many instead of just one.)

@leviadam
Copy link
Contributor

I think at the moment we have much more important things, and we should indeed leave that to the UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants