> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/platform/strategies.md). # Strategies Build holdings and move capital within a workspace. ## Strategies > **This page was called "Portfolios".** These are now **Strategies**. "Portfolio" means the workspace-level view of everything you hold. The route is unchanged; only the name is. A strategy is a named set of holdings that your capital is deployed into. It decides which pools it holds, and in what proportion. ### Why strategies exist You could deploy into pools one at a time. Most treasuries do not want to. A strategy lets you treat a group of positions as one thing. You allocate to the strategy, not to each pool, and Brava works out what that means: how much goes to each holding, which chains are involved, what has to be bridged, and in what order. One instruction, one approval, one signature — rather than one per position. It also gives you a unit to reason about. "Reserves" and "Operating yield" can hold different pools, carry different risk, and be reported on separately, inside the same workspace and the same custody arrangement. ### What a strategy contains Each **holding** is one pool, on one chain, with an amount and a share of the strategy. A strategy can span chains. If it holds Aave on Base and Morpho on Arbitrum, an allocation into it has to move capital to both — which means bridging, and bridging takes time. Brava plans that as part of the single instruction rather than asking you to sequence it. Holdings are proportional, not fixed. A holding set to 40% receives 40% of what you allocate. It does not hold a fixed amount that Brava tops up. ### Building a strategy **1. Create and name it.** From **Strategies**, create a new one. The name appears on the transaction details of everything it does, so name it for what it holds rather than when you made it. **2. Add holdings from Markets.** Markets lists every pool Brava can deploy into. Before adding one, read what backs it, where its yield comes from, and how you would exit — a rate on its own is not a reason. **3. Set the proportions.** New holdings start at 0%. Adding a holding moves nothing and commits nothing; a strategy with holdings and no allocation is a plan, not a position. **4. Allocate.** This is the point at which capital moves. ### Reading a strategy Opening a strategy shows six things. **Balance** — what the strategy holds now, across every chain. This is read from on-chain positions, not from what you allocated: if a position has grown or fallen, the balance reflects that. **Gross APY** — the blended rate across the holdings, weighted by how much sits in each. Expand it to see the components. It is gross: it does not deduct the transaction costs of getting in or out. **Earnings** — realised and unrealised, over the period you select. **Holdings** — every position: the pool, its project, its chain, its share of the strategy, and its current value. **APY movement** and **Performance** — how the rate and the value have moved over time. #### Why some of this is empty at first Balance and holdings are read live from the chain, and are populated as soon as capital lands. Earnings, APY movement and Performance are built from **indexed history** — a daily record Brava accumulates after the fact. A strategy funded today has no history, so those panels are empty, and will fill over the following days. Empty is not broken. If the balance is right and the charts are blank, the position is fine and the record is young. ### Moving capital **Actions** opens four tabs. Each states what will move, from where, to where, and the transaction fee, before you commit. #### Allocate Moves cash holdings from the workspace into this strategy, split across its holdings by their proportions. You choose the token and the amount. **Available to allocate** is the workspace's cash holdings in that token — if it reads zero, the capital is either already deployed or has not been deposited yet, and the Portfolio screen will say which. #### Redeem Moves capital out of the strategy's holdings and back to the workspace's cash holdings. Redemption draws proportionally across holdings unless you direct otherwise. What returns is not necessarily what you put in: positions accrue, and some venues have exit costs. The panel shows the final amount after fees before you commit. #### Rebalance Changes the split between holdings. The total does not change. Rebalancing sells out of one position and into another, which means transaction costs and, across chains, bridging. A rebalance that looks small in percentage terms can be expensive if it moves capital between chains. #### Transfer Moves capital from this strategy into another strategy in the same workspace. This is not a withdrawal. Capital stays inside the workspace and inside your custody arrangement throughout; only which strategy holds it changes. #### When actions are unavailable The button is disabled and states the reason: | Reason | What it means | | -------------------------------------- | ----------------------------------------------------------------------------- | | A transaction is executing | One instruction at a time, per strategy | | Balances are updating | The last transaction settled and Brava is refreshing. Brief | | The connected wallet is not authorised | Connect the wallet the workspace expects | | No holdings to act on | The strategy has no positions to move | | On-chain data unavailable | Brava cannot read your positions and will not act on numbers it cannot verify | ### What happens after you submit A progress panel opens in the corner and follows the transaction step by step. Each step names what it is doing to your capital — *Deploying funds on Base*, *Bridging to Arbitrum*, *Syncing strategy data* — and marks itself as it completes. Completed steps carry the transaction hash and a link to the block explorer. #### Cross-chain transactions A transaction that touches more than one chain runs as a sequence per chain, in order. Capital has to arrive on the second chain before it can be deployed there. Between chains, the bridge issues an **attestation** — confirmation that funds have left the source before they can be minted on the destination. This is usually the longest step, and it is normal for it to take several minutes. While it runs, the capital shows on the Portfolio screen as **capital in transit**: neither cash nor allocated, and not lost. #### When something fails A failed step says what failed and keeps its transaction hash reachable, so you can inspect it on the explorer. Failures are per-step. A cross-chain transaction that bridged successfully and then failed to deploy has moved your capital to the destination chain and left it there. Transactions holds the record. #### When Brava loses track If the progress panel says progress updates are unavailable, Brava has lost the feed reporting on your transaction. It has not lost the transaction. Further actions on the strategy stay locked until the transaction is confirmed settled, or for up to an hour and a quarter. Transactions is authoritative in the meantime. ### Editing a strategy You can add holdings, change proportions, and remove holdings. Nothing moves when you save. Edits change the strategy's definition; capital moves only through a rebalance or an allocation that you approve. A strategy can therefore sit in a state where its defined proportions and its actual holdings differ — the holdings table shows the actual. ### Where capital comes from A strategy never draws directly from your custody wallet. Capital moves in two hops: ``` Custody wallet ──deposit──▶ Workspace ──allocate──▶ Strategy ◀─withdraw── (cash holdings) ◀──redeem─── (holdings) ``` The first hop crosses the boundary between your custodian and Brava, and lives on the **Portfolio** screen. The second moves capital already inside the workspace, and lives here. The distinction matters when something looks missing. Capital that has left your custody wallet but is not in a strategy has not gone anywhere — it is cash holdings, waiting. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.brava.finance/platform/strategies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.