Bitcoin-abc: Script versioning

Created on 28 Aug 2017  路  3Comments  路  Source: Bitcoin-ABC/bitcoin-abc

One new feature added by Segwit is script versioning. As I understand it, this provides the ability to redefine opcodes without hard-forking. This seems like a useful feature to have, if only for future-proofing.

Considering that another fork may be required soon to modify the difficulty adjustment algorithm (#75), perhaps this would be a good time to add a script versioning mechanism to the protocol?

Most helpful comment

I like your idea of future proofing.
I'd personally prefer the flex-trans method for using tagged formats, as opposed to the Segwit fixed byte static format. I think this goes a step further to fp.

All 3 comments

I like your idea of future proofing.
I'd personally prefer the flex-trans method for using tagged formats, as opposed to the Segwit fixed byte static format. I think this goes a step further to fp.

Please note that SegWit added that feature, just because BlockStream wanted to add their own opcodes. (And make money of them.)(More sidechain support)

Thanks, I wasn't aware of FlexTrans. Reading up on it right now, this looks like a far better proposal than any feature added by segwit.

Please excuse my ignorance, I should have done more research before opening an issue. Will close this for now.

Was this page helpful?
0 / 5 - 0 ratings