# SCO

{% embed url="<https://www.youtube.com/watch?v=IDGNL-c2vNg>" %}

Short CALL OPerps a.k.a. SCO tokens represent selling of CALL options and are profitable in neutral or falling markets. SCO holders receive premium from LCO holders in every [settlement cycle](/operps/settlement.md) in return for enabling leveraged exposure to price rise for LCO holders. In following example, <mark style="color:yellow;">SCO holders make 0.5% profit in just 5 minutes\*</mark>.

> Token holdings are automatically rolled over to the next cycle unless sold

| Variable Name                  | Value                               |
| ------------------------------ | ----------------------------------- |
| Long CALL OPerps Token Supply  | 100                                 |
| Short CALL OPerps Token Supply | 10000                               |
| Leverage                       | 100                                 |
| Premium (per cycle)            | 50%\*                               |
| Cycle Duration                 | 5 minutes\*                         |
| Underlying Price Change        | <mark style="color:red;">-ve</mark> |

50  (50% of LCO supply i.e. 100) Tokens are transferred from LCO to SCO pool as Premium.\
No Tokens are transferred from SCO to LCO pool because market didn't rise duting the cycle.

<figure><img src="/files/2DxyfMnARdBlMZTr6FXd" alt=""><figcaption><p>SCO holders gain 0.5% in just 5 minutes*</p></figcaption></figure>

{% hint style="info" %}
Premium and cycle duration values used in this example are meant for our Arbitrum products. On Binance chain, these values are different.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ethosx.gitbook.io/operps/types-of-operps/sco.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
