Sub-Accounts
Last updated
Last updated
Console's key functionality lies in its ability to create Sub-Accounts, apply granular transaction and role policies, and manage them in a single environment, effectively segregating capital and mitigating smart contract risk. Users can create Sub-Safes using Console's interface and devise custom access control policies to suit their needs.
Taking advantage of Safe Modules, Console enables the Main Safe to manage Sub-Safes, delegating execution rights to external operators. This flexible structure caters to various scenarios, such as a fund setup where the Main Safe owners can grant certain Sub-Safe execution rights to an internal trader, limiting their operational scope. Restrictions might confine activities to specific protocols and functions, like enabling operations only on Uniswap and restricting permissions to swap functions and specified tokens.
Sub-Accounts are deployed through the Safe Factory Deployer. The Console Guard (hook) is added during the deployment transaction. This on-chain guard enforces the hierarchical relationship between the Main Account and Sub-Accounts on-chain.
Only Console Owners can initiate the creation or modification of Sub-Account configurations, which include setting Operators, signature threshold, and Transaction Policies (which authorise operational scope), all requiring on-chain Owner signatures for authentication.
This design guarantees that Sub-Account Operators are always bound by the Transaction Policies established by the Console Owners. Each Console Account is an independent Safe, of which Console Owners retain full on-chain ownership. This ensures Owners can access and manage their Safes directly from Safe’s independent UI or via contract calls at any time, reducing reliance on Brahma in any scenario.
Brahma Console allows users to segregate their risk through the creation of Sub–accounts, designed with specific permissions according to their use case.
Sub-Accounts enable users to segregate their assets into separate siloed compartments, each dedicated to specific purposes, risk profiles, or use cases. This compartmentalisation promotes organised and transparent portfolio management while also mitigating the overall risk exposure of their main Console account.
By doing so, Sub-Accounts extend Console’s functionalities by enhancing:
Segregated Risk Management: by allocating assets across multiple Sub-Accounts, users can isolate potential risks associated with specific DeFi protocols or strategies. This compartmentalisation prevents a single compromised Sub-Account from jeopardising the entire portfolio.
Granular Transparency: Sub-Accounts provide a clear breakdown of asset allocation, enabling users to track the performance of different strategies and make informed investment decisions. This transparency fosters accountability and facilitates better risk management practices.
Advanced Access Controls: through Sub-Accounts users can define granular access permissions, granting specific entities or individuals control over specific Sub-Accounts. This advanced access control set-up ensures that only authorised operators can manage and execute transactions within designated Sub-Accounts with dedicated admin vs. operator controls pre-defined.
Expanded DeFi Functionality: the integration of Sub-Accounts expands Console’s functionalities, allowing users to explore a broader range of DeFi strategies and protocols, tailored to their risk tolerance and financial goals.
Sub-Accounts can be used to manage different investment portfolios within the single overarching Main Console Account, allowing owners and operators in teams or individually to segregate and track the performance of automations and strategies including:
Trading Strategies: users can leverage Sub-Accounts to implement different trading strategies, including position management, LPing across assets or reward harvesting. Trading teams can isolate funds for distinct strategies, minimising their risk and optimising portfolio management.
Automated Transactions: Sub-Accounts can be deployed to automate specific transactions, such as setting up recurring asset purchases (DCA) and triggered auto-exits (TWAP or limit orders). More on upcoming Console Automation possibilities here.
Risk Management: Sub-Accounts are designated to cater for different risk profiles and purposes within asset management teams, based on the client’s risk and reward appetite. This aids in risk management and prevents unintended financial exposure while managing funds through Console.
Customised Access: Sub-Accounts can have different levels of access and permissions within teams. In fact, different users and teams might need different degrees of control or visibility.. For instance, a primary account owner could delegate fund management responsibilities to specific Sub-Account operators with restricted access to managing positions.
Console Owners maintain uninterrupted access to their Safe Wallet and can deploy Sub-Accounts or Safe via https://safe.global or by interacting directly with Safe contracts. Operator roles only retain access to assigned Sub-Accounts and do not have access to Main Console as per granular policy parameters. At any time Console does not have direct access to deployed accounts
