Currently, there exist a number of operational codes (opcodes) within the bitcoin protocol that have been disabled for security reasons. These script functions of the bitcoin protocol were taken out of operation in earlier versions because it was thought that there may be a bug in their implementation (OP_LSHIFT).

Although some believe that there is no reason to reactive or experiment with these opcodes, I beg to differ. These opcodes could potentially introduce value-added features to bitcoin and enhance functionality of the network. Therefore, I am wondering if there is a more efficient method of reactivating these operational codes (experimentally only at this point) than by introducing a hard fork at the protocol level ...

As bitcoin developers, it is important that we research and experiment with all possible solutions for not only scaling network capacity, but introducing new functionality.

What arguements exist in favour of reactivating these opcodes? Arguements against?

  • 1
    SegWit makes it easier to add new opcodes (more here) but I don't know it well so I can't write an answer.
    – MCCCS
    Dec 28 '20 at 10:19
  • 1
    For someone proposing an action, usually they would have some justification for why any opcode should be “reactivated”.
    – Claris
    Dec 28 '20 at 13:11
  • 1
    "Most energy-efficient way" is a strange way to frame this question, energy efficiency isn't really a concern in opcode activation
    – chytrik
    Dec 29 '20 at 11:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.