Allow plugins to have JSON-only custom ops

theoreticalbts commented 8 years ago

Currently the evaluator_registry framework is incapable of having plugins which accept only JSON custom ops (and not binary custom ops).

Here are some use cases:

(a) Plugin which accepts either JSON or binary ops
(b) Plugin which accepts only JSON ops
(c) Plugin which accepts only JSON ops in its initial version, then after some "hardfork" [1] block number accepts binary ops

The third case is the trickiest, before the hardfork date we have to ignore binary ops that would otherwise pass.

[1] This is a plugin-level hardfork, i.e. an upgrade to the plugin's consensus.

theoreticalbts commented 6 years ago

I'm not sure that this is actually a problem that's being faced by anyone.

mvandeberg commented 6 years ago

No, but it is a potential problem.

The custom binary op is an attempt to have a more streamlined custom op. The problems it introduces are more hassle than they are worth. I am in favor of deprecating the op in a hardfork.

steemit / steem

Allow plugins to have JSON-only custom ops #429