# Solution Overview
## Protocol Architecture
SHIFT bridges regulated brokerage rails to a non-custodial token layer on Solana. The protocol is built on two layers, with liquidity delivered through a B2B2C distribution model.
### Two protocol layers
**Layer 1 Backing**
SHIFT engages with a private entity that holds the backing assets. For every Series Token in circulation, this entity holds the corresponding leveraged or inverse ETF on a 1:1 basis. Backing assets are acquired through regulated brokerage rails connected via API. There are no fractional reserves. Tokens cannot be issued in excess of verified backing.
**Layer 2 Tokenization**
The SHIFT Solana program mints SPL Series Tokens backed by verified assets. Every minted token is a wallet-native asset. Once issued, tokens behave as standard SPL tokens on Solana, transferable, composable, and held in self-custody.
### Distribution model B2B2C
End users do not interact directly with the SHIFT mint and burn endpoints. Liquidity is delivered through a market-maker layer that streams continuous prices to the venues where users trade.
#### **How a user trades**
{% stepper %}
{% step %}
### Open Jupiter
The user opens Jupiter (or any integrated Solana DEX) and searches for the Series Token (e.g. TSL2L).
{% endstep %}
{% step %}
### Route the swap
Jupiter routes the swap through an RFQ (Request for Quote) liquidity layer.
{% endstep %}
{% step %}
### Get a live quote
A professional market maker streams a live quote based on the underlying ETF's NAV, plus a spread.
{% endstep %}
{% step %}
### Settle on-chain
The user accepts the quote. The swap settles on-chain in seconds. The Series Token arrives in the user's wallet.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
This RFQ-based model replaces the inefficient liquidity-pool design used by earlier RWA protocols. RFQ liquidity is always-on (24/7), capital efficient, and avoids impermanent loss for users.
{% endhint %}
### **How market makers maintain inventory**
Market makers operate on a B2B basis with the SHIFT protocol. When inventory on one side is depleted, market makers replenish it via the protocol's mint and burn endpoints, settling against the underlying ETF holdings. This keeps spreads tight and quotes responsive throughout the trading day.
### Verification Proof-of-Reserves
Proof-of-Reserves continuously verifies 1:1 backing of every Series Token in circulation. The PoR feed reads the underlying holdings and publishes the verified state of reserves. Mint operations are constrained by this feed; tokens cannot be issued beyond verified reserves.
### DeFi rails
Series Tokens are composable across the Solana DeFi ecosystem. Holders can swap on Jupiter, provide liquidity on Meteora, lend on Kamino, or trade on Orca. Standard SPL tokens, no wrappers required.
#### Step by step
{% stepper %}
{% step %}
### Back
The leveraged ETF is purchased and held 1:1 against every Series Token in circulation.
{% endstep %}
{% step %}
### Verify
Proof-of-Reserves confirms 1:1 backing.
{% endstep %}
{% step %}
### Mint
The SHIFT smart contract mints the SPL Series Token on Solana.
{% endstep %}
{% step %}
### Quote
A professional market maker streams continuous RFQ prices to Jupiter and other venues.
{% endstep %}
{% step %}
### Trade
The user buys, sells, LPs, or lends the Series Token across Jupiter, Meteora, Kamino, and Orca 24/7, permissionless
{% endstep %}
{% endstepper %}
### Daily Rebalancing
{% hint style="info" %}
SHIFT does not perform rebalancing. The leverage is delivered by the underlying ETF (e.g., Direxion TSLL), which manages its own daily reset internally. SHIFT simply tokenizes the ETF position 1:1. Nothing happens at 4 PM ET inside the SHIFT protocol.
{% endhint %}
### How leveraged ETFs work
Leveraged and inverse ETFs are designed to deliver a multiple (e.g. 2× or 3×) of the daily return of their underlying index. To maintain that target multiple, the ETF issuer rebalances the fund's internal exposure, typically through options and other derivative instruments, once per trading day at the close (around 4 PM ET).
This is the mechanism that prevents total wipeout. In extreme volatility, the ETF reduces exposure as values drop, allowing the fund to survive sharp drawdowns rather than being forced to zero. A trader who holds the ETF can endure a crash and participate in the subsequent recovery, something that is structurally impossible with a borrowed-leverage position that has been liquidated.
### Why this matters for SHIFT holders
Because SHIFT (indirectly) holds the underlying leveraged ETF on a 1:1 basis, every Series Token inherits the ETF's survival mechanism. NAV declines on adverse moves, but the position cannot be force-closed. The holder remains exposed through the cycle and can participate in any recovery.
This is the structural difference from a perpetual futures position. With a perp, a temporary dip below the margin call threshold liquidates the position permanently, and the trader cannot ride the recovery. With a SHIFT Series Token, the same volatility produces a NAV swing, but the position survives.
### Cost of leverage
Leveraged ETFs incur an internal cost for maintaining their leveraged exposure. This cost is reflected in the asymmetry of returns: a 3× ETF typically captures slightly less than 3× on the way up, and slightly more than 3× on the way down, over short horizons.
As an illustration: if the underlying moves +3% on the day, a 3× long Series Token might gain roughly 2.85–2.90%. If the underlying moves −3%, the same Series Token might lose around −3.10%. The gap reflects the embedded cost of running the leveraged exposure.
### Compounding over multi-day periods
Daily resets cause the cumulative return of a leveraged product to diverge from a simple multiple of the underlying's cumulative return:
* **Trending markets:** compounding can cause the leveraged token's return to exceed a static multiple of the underlying's cumulative move
* **Range-bound markets:** compounding produces drag the token underperforms a static multiple of the underlying's cumulative move
Holders should understand that daily-reset leveraged products are designed for short- to medium-term horizons. Multi-month holds in choppy markets can produce material drag relative to a static-multiple expectation.
### Peg Stability
A SHIFT Series Token is designed to trade close to the NAV of its underlying ETF. Price stability is maintained through three mechanisms.
#### 1. 1:1 backing
Every Series Token in circulation is backed 1:1 by the underlying ETF. The backing is verified. There are no fractional reserves.
#### 2. RFQ market-maker liquidity
Professional market makers stream continuous RFQ (Request for Quote) prices to Jupiter and other Solana venues. Quotes are referenced to the underlying ETF's NAV, plus a spread that compensates the market maker for inventory risk and execution costs.
Market makers replenish inventory through SHIFT's mint and burn endpoints, settling against the underlying ETF holdings. This continuous arbitrage between the on-chain price and the ETF NAV keeps the Series Token's market price closely tracked to its backing.
#### 3. DeFi liquidity
Series Tokens trade on multiple Solana DEXs (Jupiter, Meteora, Kamino, Orca). Distributed liquidity across venues reduces single-venue dislocations and tightens spreads.
#### Trading hours and spreads
Trading is available 24/7. Spreads vary based on the state of the underlying market:
| **Market state** | **Typical spread** | **Why** |
| ------------------------- | ------------------- | -------------------------------------------------------------------------------- |
| **U.S. market hours** | Tightest | Underlying ETF actively trading; market makers can hedge inventory in real time |
| **Off-hours / overnight** | Wider | Underlying market closed; market makers carry more inventory risk |
| **Weekends** | Widest (up to \~3%) | No primary-market access for two days; inventory cannot be replenished or hedged |
Spreads tighten as the underlying market reopens and market makers can rebalance their inventory.
---
# 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-2.md?ask=
```
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.