Strategy Vaults - Documentation

Overview

Strategy Vaults is organized as a route-based BTC deployment system. Users authenticate into a single account session, select a route, fund a BTC deposit address, and receive route-level credit after network confirmation and route intake processing.

Each route maintains its own yield policy, liquidity reserve, withdrawal window, and internal risk label. Published APY is shown as a route average, not a point-in-time tradeable rate. The active route panel remains the source of current operating values for new deployments and withdrawal review.

Protocol model

Strategy Vaults uses a layered operating model so deposits, accounting, liquidity policy, and account review can remain separated while still presenting a single route workflow.

Custody intake

BTC enters through a route-specific funding instruction and remains uncredited until network confirmation requirements are met.

Route ledger

Confirmed deposits are written to a route ledger that tracks pending, credited, deployed, and withdrawable balances in BTC terms.

Liquidity engine

Each route maintains its own liquidity reserve, target deployment posture, and withdrawal servicing window.

Proof layer

Account activity, route age, and operating status are surfaced through the portfolio workspace and route views.

State	Description
Pending confirmation	Deposit has been broadcast or detected but has not yet reached the route confirmation requirement.
Credited	Deposit has passed confirmation checks and is recognized by the route ledger.
Deployed	Credited BTC has moved from intake status into the active route balance used for yield accrual.
Withdrawal queued	A withdrawal request has been submitted and is waiting for the route window or internal liquidity release.
Settled	BTC has left the route and the corresponding route balance has been reduced.

Account access

Strategy Vaults account access is session-based. Users enter an email address, complete password setup or password verification, and then access the portfolio workspace under the authenticated account email.

Email addresses require a valid address format and at least four characters before the @ symbol.
New accounts create a password during initial sign-in. Existing accounts enter the previously stored password.
Password recovery is initiated through the I forgot password? link in the sign-in flow.
Authenticated sessions are reused across the portfolio workspace and route deposit flow.
Direct BTC funding instructions are opened from an authenticated session so route actions stay tied to the account email.

Route catalog

Route	Code	Primary mechanism	Average APY	Rate review cadence	Standard withdrawal window
Strategy Bitcoin	STRCB	Bitcoin-native tokenized STRC vault for core BTC yield	11.5%	Scheduled review	24h
Treasury Reserve	STRCBT	Bitcoin-native tokenized STRC vault for reserve-focused BTC allocation	5.6%	Scheduled review	24h
Instant Liquidity	STRCBL	Bitcoin-native tokenized STRC vault for faster-liquidity BTC positioning	21.4%	High-frequency review	24h
Strategy ETH	STRCBE	Bitcoin-native tokenized STRC vault for ETH-linked yield exposure	8.4%	Weekly review	48 hours
Growth Rotation	STRCBG	Bitcoin-native tokenized STRC vault for higher-yield BTC rotation	39.5%	Tactical review	48 hours

Route APY values, flow, and TVL are shown in the app and may update as route earnings, reserve policy, and available liquidity change.

Deposit lifecycle

Deposits are initiated from the vault route interface or directly from eligible portfolio route rows. After route selection, users enter a BTC amount, review the route ticket, and choose Deploy.

Select the intended route and confirm the displayed APY, flow, and TVL.
Enter a deposit amount of at least 0.05 BTC.
Review the projected balance and annualized BTC yield in the route ticket before continuing.
Open the BTC funding modal and send the exact amount to the displayed wallet address or scan the QR code.
The transaction remains pending until it reaches 6 network confirmations.
After confirmation, BTC is credited to the route ledger and moved into deployable route balance.
Portfolio balances and route-level availability update after credit is recognized by the route process.

Deposit instructions are delivered as a BTC address and matching QR payload. Users should fund only from the Bitcoin network and should confirm both the route and amount before sending.

Deposit stage	Control point
Address confirmation	User confirms the route and address before broadcast.
Network confirmation	BTC remains uncredited until the route confirmation requirement is satisfied.
Ledger credit	Confirmed BTC is written to the route ledger and becomes visible to the account session.
Route deployment	Credited BTC enters the route balance used for route-specific accrual.

Yield accrual and rate publication

Strategy Vaults publishes route APY as an averageized route rate derived from the route's earning profile, operating spread, and liquidity reserve requirements. APY is intended to describe the route's current earning posture rather than a locked forward contract rate.

Input	Effect on published APY
Gross route earnings	Increase the route average when earnings remain stable and route utilization stays within policy.
Liquidity reserve requirements	Reduce distributable yield when larger cash or BTC buffers are required to protect exit windows.
Volatility and venue stress	Can compress route APY, especially in low-risk and medium-risk routes with active market exposure.
Route review cadence	Controls how quickly updated route conditions are reflected in published averages.

Accrual is recorded in BTC terms once a deposit has moved from pending confirmation into deployed route balance.
Risk-free routes are managed to keep APY schedules steadier in ordinary conditions.
Low-risk and medium-risk routes may see APY compression when volatility, liquidity stress, or reserve requirements increase.
The portfolio workspace displays a blended APY derived from current route allocations, not a separate portfolio rate engine.

Withdrawals

Withdrawals are opened from the same route row through the Withdraw tab. The route ticket shows the requested amount, available balance, and the applicable route window before a withdrawal preview is prepared.

Risk-free and Instant Liquidity routes use a standard 24h withdrawal window.
Strategy ETH and Growth Rotation use a standard 48 hours withdrawal window.
If the requested amount exceeds the route balance, the request must be reduced before review can continue.
MAX fills the withdrawal amount from the route's available balance.

Withdrawal timing is influenced by route liquidity, reserve release, and any active route review window. Standard route windows are intended to describe normal operating cadence rather than an instantaneous exit guarantee.

Risk labels

Strategy Vaults uses internal product classifications to describe how APY schedules and withdrawal timing are expected to behave under normal and stressed conditions.

Label	Operational meaning
Risk-free	Fixed APY schedule not intended to reset during ordinary volatility and standard liquidity conditions.
Low risk	APY may compress moderately during higher volatility or lower liquidity periods, while standard withdrawal windows remain in force.
Medium risk	APY and settlement timing may change more materially during stressed conditions, venue-level delays, or active rotation windows.

Portfolio workspace

The portfolio workspace shows total BTC deployed, blended APY, projected 1-year BTC yield, route-level allocation, and recent account activity. Each route row can be expanded to reopen deposit and withdrawal actions without leaving the portfolio page.

Net BTC deployed reflects the aggregate funded BTC recorded across active routes.
Blended APY represents the weighted average APY of current route allocations.
Projected 1Y BTC yield estimates route-level annual output based on the current allocation mix.
Recent activity records deposit and withdrawal events once route history is available.

Operational standards

Funding controls

Only BTC funding is supported in the active route workflow. Users should not send non-BTC assets to a route address.

Authentication

Deposit instructions are opened from an authenticated account session to keep route actions tied to the account email.

Route liquidity buffers

Each route maintains a reserve policy intended to support normal withdrawals without forcing immediate full route unwind.

Address handling

Users should copy the full wallet address from the funding modal or scan the QR directly to reduce manual entry errors.

Rate review

Published APY should be reviewed at the route level before each new deployment, since route conditions can change independently.

Settlement discipline

Withdrawal windows should be read together with route risk labels because active routes may require longer exit handling under stress.

FAQ

What causes a route APY to move lower even when deposits remain open?

Route APY can compress when gross route earnings fall, liquidity reserve requirements increase, or a route shifts to a more defensive operating posture during volatility or venue stress.

Why can a withdrawal remain within review after the standard route window has started?

Standard route windows describe normal servicing cadence. A withdrawal can remain in review if the route is releasing liquidity, settling venue balances, or processing a route-level rebalance before final exit.

How does credited balance differ from deployed balance?

Credited balance refers to BTC that has completed confirmation checks and has been recognized by the route ledger. Deployed balance refers to credited BTC that has moved into the active route balance used for route-level accrual.

What distinguishes a Risk-free route from a Low risk route operationally?

Risk-free routes are managed to keep APY schedules steadier in ordinary conditions and generally operate with more conservative reserve treatment. Low risk routes can accept more rate variability in exchange for higher target earnings while still maintaining defined withdrawal servicing standards.

Product documentation