Move virtual ops to plugins

[vikramrajkumar]

From @theoreticalbts on February 12, 2016 17:22

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: cryptonomex/graphene#246 cryptonomex/graphene#570

Copied from original issue: cryptonomex/graphene#571

[abitmore]

We don't want to break numbering of op history so far. Closing.