OP_CC: A simple introspection opcode to enable cheaper consolidations

[reardencode]

@billymcbip

The problem is that the consolidation transaction can only roll value forward into the same contract. To pay a third party (new SPK), you need a second transaction spending the consolidated output.

Sure, but all we really care about is bytes not transactions. Using OP_CCV uses 5 extra bytes per consolidated input, plus a 1-input, 1-output transaction compared to OP_CC. It is a bit more expensive, but still much cheaper than current consolidations. The OP_CCV-style could be broadcast as a TRUC transaction using package relay, so it wouldn’t even need a separate fee input if the consolidated output is spent immediately.