Enable OP-Codes & Scripting?

[crazy_rabbit]

While I am a novice programmer, I am intrigued by the possibilities of scripting with Bitcoin but noticed that they are currently disabled, and I understand that most likely for good reason. Are there any thoughts about enabling them sometime soon? What would need to be done to enable them?

[1715701246]

1715701246

[1715701246]

1715701246

[1715701246]

1715701246

[1715701246]

1715701246

[1715701246]

1715701246

[Peter Todd]

They are enabled already on Testnet so you can try your experiments there.

[Gavin Andresen]

http://bitcoin.stackexchange.com/questions/5664/will-general-non-standard-transactions-ever-be-allowed

[TheBitcoinTote]

@Crazy_rabbit

Can or has terracoin loosen the isStandard() check?

[Remember remember the 5th of November]

Correct me if I am wrong, but don't most op-codes already work? Isn't like OP_CHECKSIG, OP_WHATNOT already used in Bitcoin? Aren't these op-codes?? And isn't that considered "scripting"?

[piotr_n]

Most of the opcodes are enabled - only these are disabled:

Code:

0x7e/*OP_CAT*/
0x7f/*OP_SUBSTR*/
0x80/*OP_LEFT*/ 
0x81/*OP_RIGHT*/ 
0x83/*OP_INVERT*/
0x84/*OP_AND*/
0x85/*OP_OR*/
0x86/*OP_XOR*/ 
0x8d/*OP_2MUL*/
0x8e/*OP_2DIV*/ 
0x95/*OP_MUL*/
0x96/*OP_DIV*/
0x97/*OP_MOD*/
0x98/*OP_LSHIFT*/
0x99/*OP_RSHIFT*/

But they seem pretty useless, anyway.

All the other opcodes should work fine, as soon as you manage to convince a miner to include such a tx for you, in a block.
I'd suggest bribing it, by leaving a decent fee - eventually they will realize that mining a non-standard txs might be a good business opportunity.

[crazy_rabbit]

@Crazy_rabbit

Can or has terracoin loosen the isStandard() check?

I'm not the dev for Terracoin, and for the moment I'm not really involved in anything TRC related. :-/

[gmaxwell]

But they seem pretty useless, anyway.

alas, actually they're useful. With them you could validate a SPV proof for a cross chain txn, for example.

[btc4ever]

Can anyone provide the history as to why the disabled opcodes were disabled in the first place?   Or were they simply never implemented?

[gmaxwell]

Can anyone provide the history as to why the disabled opcodes were disabled in the first place?   Or were they simply never implemented?

The implementations were buggy.  In the case of the LSHIFT operator there was a remotely triggerable crash. All the operators that changed the sizes of types basically got disabled as a precautionary measure.