# Position Lifecycle

<mark style="color:$info;">This section describes how a leveraged prediction market position moves from creation to settlement. All user actions occur through the originating front-end. Dimes executes and maintains the underlying hedge and synthetic exposure through Multiply.</mark>

{% stepper %}
{% step %}
**Opening a Position**

<mark style="color:$info;">The user selects:</mark>

* <mark style="color:$info;">a supported prediction market</mark>
* <mark style="color:$info;">a direction (YES or NO)</mark>
* <mark style="color:$info;">a leverage level</mark>
  {% endstep %}

{% step %}
**The terminal requests a quote from Multiply, passing information such as:**

* <mark style="color:$info;">market and trader</mark>
* <mark style="color:$info;">direction</mark>
* <mark style="color:$info;">requested leverage</mark>
* <mark style="color:$info;">notional demand and collateral value</mark>
  {% endstep %}

{% step %}
**Multiply evaluates:**

* <mark style="color:$info;">current venue price and market microstructure</mark>
* <mark style="color:$info;">hedgeability of requested size within slippage bounds</mark>
* <mark style="color:$info;">required collateral and margin</mark>
* <mark style="color:$info;">per-market, per-side, and per-user cap headroom</mark>
  {% endstep %}

{% step %}
**Multiply returns a firm executable quote that includes:**

* <mark style="color:$info;">entry price and execution cost</mark>
* <mark style="color:$info;">required collateral</mark>
* <mark style="color:$info;">maximum allowed size (if clipped by caps or depth)</mark>
* <mark style="color:$info;">implied liquidation price</mark>
* <mark style="color:$info;">an expiry timestamp — the offer is only valid for a limited window. The</mark> <mark style="color:$info;"></mark><mark style="color:$info;">`expires_at`</mark> <mark style="color:$info;"></mark><mark style="color:$info;">field in the API response indicates the deadline. If the user does not execute before this time, the offer becomes invalid and a new quote must be requested.</mark>
  {% endstep %}

{% step %}
**Hedge-first execution**

<mark style="color:$info;">If the user accepts, the front-end submits an execute call. Multiply executes the hedge on the external venue first.</mark>

* <mark style="color:$info;">Only if the hedge fills within slippage bounds is the position created, user collateral is locked, and the synthetic leveraged exposure is established.</mark>
* <mark style="color:$info;">If the hedge fails or slippage exceeds bounds, the order is rejected and no position is created.</mark>
  {% endstep %}

{% step %}
**Active monitoring**

<mark style="color:$info;">The position becomes active and appears in the front-end's portfolio view. Once active:</mark>

* <mark style="color:$info;">Multiply monitors margin, venue health, and eligibility continuously</mark>
* <mark style="color:$info;">Limits and maximum leverage evolve dynamically based on market conditions</mark>
* <mark style="color:$info;">The market may enter close-only if any eligibility threshold is breached</mark>
  {% endstep %}

{% step %}
[**Leverage decay (J-factor)**](https://docs.dimes.fi/leverage-and-risk/leverage-decay-j-factor)

* <mark style="color:$info;">J-factor is Multiply's dynamic risk engine. It continuously monitors depth profile, odds dynamics, open interest microstructure, and resolution conditions, defining when leverage should be reduced.</mark>
* <mark style="color:$info;">Leverage reduction is triggered only when microstructure conditions warrant it. On the winning side, this means leverage often remains intact through resolution. On the losing side, deteriorating microstructure typically triggers deleverage earlier, protecting both the user and the facility.</mark>
  {% endstep %}

{% step %}
**Liquidation** **(if triggered)**

* If a user's remaining collateral falls to maintenance margin at any point during the position lifecycle, Multiply liquidates the position. The hedge is unwound on the originating venue and all execution costs are deducted from the user's collateral. Because J-factor proactively reduces leverage as the position deteriorates, users are significantly better protected than under traditional frameworks. Forced liquidations under Multiply are rare.

<figure><img src="https://1022419315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN1e2ZWHiYJgbZcBafIka%2Fuploads%2FcIKP1epXcEkDTmlMZR8O%2Fimage.png?alt=media&#x26;token=8476eff5-b0a8-4fb4-af03-c828c49ed8ec" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}
