Author

Topic: Disabled script operands (Read 849 times)

legendary
Activity: 1204
Merit: 1015
September 27, 2011, 03:50:48 PM
#5
They're not disabled because there are known attacks against scripts using them (although there may be for some), they are disabled because they are not needed (yet).
No, that's exactly why they were disabled:
https://en.bitcoin.it/wiki/Incidents#LSHIFT_and_RETURN_bugs

More info:
https://bitcointalksearch.org/topic/why-so-many-op-codes-are-disabled-37157
https://bitcointalksearch.org/topic/reliance-upon-transactions-vs-reactions-to-incidents-28861
sr. member
Activity: 462
Merit: 250
September 27, 2011, 03:49:36 PM
#4
Thanks.
legendary
Activity: 905
Merit: 1012
September 27, 2011, 01:14:28 PM
#3
They're not disabled because there are known attacks against scripts using them (although there may be for some), they are disabled because they are not needed (yet).

EDIT: I stand corrected.
sr. member
Activity: 462
Merit: 250
September 27, 2011, 11:46:43 AM
#2
Bump.  I'd really appreciate some help with this, because the term "script" is hard to google usefully for. :-)
sr. member
Activity: 462
Merit: 250
September 27, 2011, 07:22:45 AM
#1
I'd be grateful for pointers to the following:

  • Good discussions of the specific security threats posed by the currently disabled Script operands and the prospects for enabling them in the future.
  • Good discussions of extensions to the scripting language, their utility, the security threats they pose, and the prospects for their future implementation.
  • Good discussions of how and why to implement the currently disabled operands.
  • Good discussions of the speed of adoption of updated clients and mining software.
Jump to: