# Risk Management

### SHIFT & Tokenized Equity Risks

Holding a SHIFT Series Token carries the underlying market risk of the leveraged ETF it represents, plus additional risks specific to a tokenized, on-chain wrapper. Users should understand each category before trading.

#### Market and leverage risk

* **NAV decline:** A Series Token's NAV moves with the value of its holdings, e.g., leveraged ETFs. A 3× long token's NAV can fall meaningfully on adverse moves in the underlying. NAV cannot go below zero, but a holder may incur substantial losses up to the total purchase price.
* **Volatility decay:** Daily-reset leveraged products compound daily. In trending markets, compounding can exceed a simple multiple of the underlying's cumulative return. In choppy, range-bound markets, compounding produces a drag known as volatility decay. This is a property of the underlying ETF, not specific to SHIFT.
* **Inverse risk:** Short Series Tokens carry the same compounding properties in reverse. Sustained trends in the wrong direction can erode NAV rapidly.

#### Custody and counterparty risk

* **Brokerage custody:** Backing ETFs are held in segregated accounts at FINRA-registered, SEC-regulated brokerage partners. A failure or operational issue at the brokerage layer could affect the protocol.
* Tokenizer risk: All assets held by the Series are tokenized by a third party. Third-party failure can reduce the timing of buying or selling Series tokens.
* **ETF issuer risk:** The leveraged and inverse ETFs are issued by third parties (e.g., Direxion). The issuer's ability to maintain the daily-reset leverage and operate the fund is a dependency of the SHIFT product.
* **Market-maker risk:** User-facing liquidity is provided by professional market makers via RFQ. While market makers are bound to spread KPIs, quotes during off-hours and weekends carry wider spreads to reflect inventory risk.

#### Smart contract and oracle risk

* **Contract risk:** All SHIFT smart contracts are audited. Audits reduce but do not eliminate risk. See the Resources / Audits section.
* **Oracle risk:** SHIFT uses Chainlink Proof-of-Reserves to verify backing on-chain. Oracle failure or manipulation could affect the integrity of the published reserve data.

#### Liquidity and execution risk

* **Trading liquidity:** Series Tokens trade on Solana DEXs (Jupiter, Meteora, Kamino, Orca). Pool depth varies; large orders may incur slippage.
* **Spread variability:** RFQ spreads are tightest during U.S. market hours and widest on weekends (up to \~5%). Holders trading in off-hours should expect to pay or receive a wider spread relative to the underlying ETF NAV.
* **Backing operations window:** Underlying ETF purchases and sales operate during U.S. market hours (24/5). User-facing trading remains 24/7 via RFQ liquidity.

#### Regulatory and jurisdictional risk

* **Restricted jurisdictions:** Series Tokens are not offered to U.S. or U.K. persons, nor to persons in certain other restricted jurisdictions. Full eligibility rules are documented in the Terms of Use and Risk Disclosure.
* **DAO LLC structure:** Tokens are issued under the Marshall Islands DAO LLC framework as membership-interest tokens. Holders' rights differ from those of typical equity holders. For more information, please see the legal ecosystem chapter. \[LINK]

{% hint style="info" %}
This page is a summary. Full risk disclosures are published in the Risk Disclosure document linked in the Resources section.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://shiftrwa.gitbook.io/shift_education/shift_learn-1.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.