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

Move virtual ops to plugins #571

Closed
theoreticalbts opened this issue Feb 12, 2016 · 0 comments
Closed

Move virtual ops to plugins #571

theoreticalbts opened this issue Feb 12, 2016 · 0 comments

Comments

@theoreticalbts
Copy link
Contributor

It seems like it would be useful to have plugins able to create v-ops, and re-work existing core v-ops into plugins. Then if we upgrade v-ops in any way, clients can use their configuration to choose what v-ops are generated and whether they break operation history. This approach loses consistent numbering of op history and gives everybody different v-op set based on their configuration -- but that is OK. V-ops and operation history are inherently things which are used by particular UI implementations and are not core features. Related: #246 #570

@vikramrajkumar
Copy link
Contributor

This issue was moved to bitshares/bitshares-core#157

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