Is Ripple's Contract language intended to be Turing complete or sub-Turing complete ?

The wiki seems to imply Turing-completeness because no restrictions on jumps are specified here https://ripple.com/wiki/Contracts#Foundational_Ops.

Which is it and what (if any) is the actual intention ?

Cheers ...

Alex Kravets

Posted 2013-03-22T07:20:27.363

Reputation: 518

1Cool, I didn't even know Ripple had contracts! – ripper234 – 2013-03-22T08:43:41.933

1If the language is Turing complete, they will promptly have to be disabled :-) – Alex Kravets – 2013-03-22T09:33:31.933

Answers

It should be Turing complete. However, every time a contract is invoked, the maximum number of operations the contract can perform is limited. Operations that access a contract must specify an operation count limit to get a limit higher than the default. Higher limits require higher transaction fees.

David Schwartz

Posted 2013-03-22T07:20:27.363

Reputation: 46 931

Does the Turing completeness of Ripple allow for denial of service attacks with infinite loops? – goodguys_activate – 2013-12-15T01:35:05.040

@makerofthings7 No, there's a strict limit on how much work a contract can do. – David Schwartz – 2014-02-23T21:28:17.053