In contract evaluation, when a stopping condition triggers, what happens to subsequent lines?

In contract evaluation, when a stopping condition triggers, what happens to subsequent lines?

• A. All lines are evaluated
• B. It triggers an error
• C. The contract stops evaluating and ignores subsequent lines
• D. The system restarts

Answer: (C)

When a stopping condition is met, the evaluation flow ends immediately and any lines that come after are ignored. This acts like an early exit: the contract halts at that point, preserving the state up to the stopping moment and preventing any further actions from being performed. This approach keeps the outcome deterministic and avoids applying instructions that assume the stop condition hasn’t occurred yet. It’s not an error or a restart; it’s a deliberate halt designed to finalize the contract’s behavior once the stop condition is satisfied.

When a stopping condition is met, the evaluation flow ends immediately and any lines that come after are ignored. This acts like an early exit: the contract halts at that point, preserving the state up to the stopping moment and preventing any further actions from being performed. This approach keeps the outcome deterministic and avoids applying instructions that assume the stop condition hasn’t occurred yet. It’s not an error or a restart; it’s a deliberate halt designed to finalize the contract’s behavior once the stop condition is satisfied.