# Glossary ### **Overview** This glossary defines key terms and concepts used throughout the Brava platform and documentation. It’s designed to help new users, allocators, and developers understand Brava’s architecture and terminology. *** #### **A** **Allocation**\ The process of deploying funds from a workspace’s SAFE wallet into specific holdings within a portfolio. Allocations are executed as on-chain transactions that can distribute capital across multiple pools or chains in one action. **Asset**\ Any supported token or instrument (e.g. USDC, USDT, DAI, or tokenised real-world assets) held or managed within a workspace or portfolio. *** #### **B** **Brava**\ A non-custodial platform providing professionals and institutions access to stablecoin and real-world-asset (RWA) credit markets. Brava automates allocation, execution, and reporting across self-custodied vaults. **Bridge / Bridging**\ The process of moving assets across blockchain networks. Brava automates bridging as part of allocation, transfer, and withdrawal transactions, users never have to perform bridging manually. *** #### **C** **Client Account**\ A segregated workspace representing one managed client, fund, or treasury mandate. **Custody (Self-Custody)**\ A model where users retain full control of their assets. Brava never takes custody, all transactions are executed via the user’s underlying SAFE wallet. *** #### **D** **Dashboard**\ The main Brava interface where users can view balances, performance analytics, and manage workspaces, portfolios, and transactions. **Deposit**\ A transaction that moves funds from an external wallet (e.g., Fireblocks, Utila, Metamask) into a workspace’s SAFE wallet. Deposits represent the first step before allocating capital into portfolios. **Diversification**\ The act of distributing assets across multiple holdings, protocols, or chains to reduce risk exposure. *** #### **F** **Fireblocks / Utila / Ledger Enterprise**\ Institutional custody and wallet infrastructure providers commonly used to connect to Brava workspaces. **Funds (Allocated vs Unallocated)** * **Allocated Funds:** Capital that has been deployed into one or more portfolios. * **Unallocated Funds:** Capital sitting in the workspace SAFE wallet awaiting deployment. *** #### **H** **Holding**\ An individual yield-bearing instrument within a portfolio, such as a lending pool, liquidity vault, or tokenised RWA credit. *** #### **M** **Managed Fund (Brava Managed Fund)**\ A professionally managed investment vehicle offered by Brava, providing diversified exposure to digital credit and RWA markets. Distinct from user-managed portfolios within the Brava platform. *** #### **P** **Portfolio**\ A structured grouping of holdings (stablecoin and RWA assets) within a workspace. Portfolios define allocation weights, performance metrics, and yield strategies. Each workspace can have multiple portfolios. **Portfolio Allocation**\ The proportional distribution of capital across holdings within a portfolio. **Portfolio Rebalance**\ The act of updating allocation weights within a portfolio, typically triggered by a rebalance transaction to reflect new strategy parameters. **Proportional Withdrawal / Transfer**\ A transaction that maintains the relative weighting of holdings while moving or withdrawing capital. *** #### **R** **Rebalance Transaction**\ An on-chain operation that applies saved portfolio changes (drafts or edits) to update the portfolio’s active allocation. **Real-World Assets (RWA)**\ Tokenised representations of off-chain financial instruments, such as trade finance, private credit, or treasury bills, integrated into Brava’s investment strategies. *** #### **S** **SAFE Wallet**\ A smart-contract wallet that underpins every workspace in Brava. It ensures asset segregation, permission management, and secure execution of transactions. **Segregation**\ A structural design principle in Brava ensuring that each workspace’s assets and portfolios remain completely separate from others. **Self-Custodial Architecture**\ Brava’s infrastructure model where users retain full control of funds while the platform automates transactions and reporting. *** #### **T** **Template Portfolio**\ A pre-configured portfolio blueprint designed to help users quickly deploy capital into common yield strategies. **Transaction**\ Any blockchain operation executed through the Brava platform.\ There are five main types: * **Deposit:** Add funds to a workspace. * **Allocate:** Deploy funds into portfolio holdings. * **Transfer:** Move funds between portfolios. * **Redeem:** Return allocated funds from a portfolio to the workspace wallet. * **Withdraw:** Return funds from the workspace wallet to the connect wallet. **Transfer**\ Moves capital proportionally from one portfolio to another within the same workspace, preserving allocation weights. *** #### **W** **Wallet (Connected Wallet)**\ The user’s externally managed Web3 or custody wallet (e.g. Fireblocks, Utila, Metamask) connected to Brava for authentication and transactions. **Withdrawal**\ A transaction that proportionally withdraws capital from the workspace SAFE wallet to the client's connected wallet. **Workspace**\ A self-contained environment in Brava that represents one client or fund account. Each workspace has its own SAFE wallet, portfolios, and reporting. Workspaces ensure complete segregation of assets, activities, and permissions. *** #### **Y** **Yield**\ The return generated from deployed holdings within a portfolio. Yield may come from lending interest, protocol rewards, or tokenised credit flows. --- # Agent Instructions: 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://docs.brava.finance/resources/glossary.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.