FAQs
Brahma FAQs
2What is Brahma?
Brahma builds solutions to make DeFi execution and custody efficient. Brahma focuses on improving the UX of performing and automating DeFi interactions from self custody, while mitigating security risks involved in the process. Brahma Console is the cornerstone of this vision, providing a holistic solution for on-chain self-custody and transaction execution, with advanced access control and automation capabilities designed for a multi-player, team experience.
Before building Console, Brahma built and operated multiple Smart Contract Vaults for automating on-chain operations. Brahma Vaults have ceased operations for the team to focus fully on Console, which offers an upgraded, scalable, and more secure architecture for automations.
2. Did Brahma raise outside funding?
Yes, Brahma has raised from renowned investors such as Framework, Greenfield, Maven11, Zee Prime Capital, Cherry, Dialectic, Bitscale, and more.
Does Brahma have a token?
No
Are Brahma vaults still operational?
Brahma Vaults has reached the conclusion of its operational phase, paving the way for our dedicated focus on the advanced Brahma Console. Currently, Vaults have transitioned to a withdrawal-only mode, accessible to all users with existing deposits. We strongly advise our users to promptly withdraw their funds, as they are no longer actively managed and remain idle in the vaults. A recap of the vaults and more details can be found here.
General Console FAQs
1. What is the timeline for Brahma Console’s Main release?
Brahma Consoles Alpha Phase has rolled out across multiple releases with 1:1 team feedback loops throughout.
The pilot launch entailed features for delegated operational set-up via Sub-Account modules, Transaction policies set-up, and granular access control. With an initial DCA automation capability via CoWswap, Console also enlisted preferential gas payment token selection, ERC-20-enabled deposits, advanced transaction management, and batched executions.
Brahma Console is set for its main release in December 2023 with advanced automation and execution capabilities on your Safe with capabilities to pre-approve specific automation routines and further deepen transaction policies for asset managers, DAOs, teams, and individuals.
2. What is the initial fee structure charted for Console users?
3. What is a Safe Plugin (Safe Module)?
In the Safe protocol, Safe Plugins are utilised to extend Safe wallet functionalities. These act as smart contracts, implementing custom features while keeping the module logic separate from Safe's core contract.
4. How does Console automate actions without taking custody of funds?
Console leverages the secure infrastructure of Safe, a non-custodial smart account layer, and strengthens it with Console Safe Plugin and Hooks to automate transactions based on user-defined triggers without retaining custody of your funds. The funds are always sitting in the user's Safe, while the execution of a transaction is delegated to a bot, based on a specific trigger.
For more info, refer to the next tab on LRT Automation FAQs.
5. What are the risks involved in using Console Automations?
As specified in the risks assessment tab.
LRT Automation FAQs
1. What tokens can be automated using this feature?
The automation feature currently supports ezETH by Renzo and weETH by EtherFi liquid restaking tokens. Users can set automated buy or sell orders for these tokens based on predefined market conditions.
2. Can users automate other tokens besides ezETH and eETH?
Currently, the automation feature is specifically tailored for ezETH and eETH tokens. However, future releases may include additional tokens based on user demand and platform developments.
3. Are there any restrictions on the number of tokens users can automate?
There are no upper limits to the number of ezETH and eETH tokens that users can automate, giving them full flexibility within their Console holdings.
4. Is there a minimum token amount required to initiate automation?
Due to high mainnet gas fees, the minimum size for automation is set at 10 ETH, to ensure that the operations are economical for users. Users should hold the token amount in their Console Safe to be able to start an automation.
5. How frequently automation settings for tokens be adjusted?
Automation starts with a max slippage of 0.1%, methodically increasing with each retry, up to a 5% limit, to optimize order execution rates. Therefore, the maximum theoretical slippage incurred will be 5%, but that slippage level will only be reached after 10+ retries over multiple blocks and only if the market condition meet the slippage condition.
6. What are the risks associated with the LRT automation?
Rapid price fluctuations may affect swap effectiveness. Users should be mindful of prices temporarily dropping and rebounding before execution, potentially leading to suboptimal outcomes. If prices drop faster than set limits or swap routes are unavailable, the automation may not execute transactions within desired parameters. Users are advised to monitor market conditions closely and adjust settings accordingly to mitigate these risks. For more information, head over to Risks.
7. How are fees calculated for using the automation feature?
A 0.5% execution fee inclusive of the gas fee for the trade is applied to the input tokens involved in swap transactions, collected only upon automation execution. There are no set-up or additional fees.
The automation setup costs gas as per the network requirement, including the gas cost incurred in setting up a new SubAccount Safe, as well as registering the automation with its required approvals.
8. Can users customise swap routes?
No. Swap routes are automatically handled based on the most optimal quote between 1inch, 0x Matcha, or LiFi.
9. How does the automation ensure the best swap rates?
Automation is designed to secure the best available rates by evaluating and computing real-time market price and liquidity across multiple routes, ensuring users benefit from competitive rates even as market conditions shift.
10. Are there additional charges with specific swap routes?
No.
Brahma Connect FAQs
What is Brahma Connect?
Brahma Connect is a tool designed to streamline transaction execution for users. It enables secure and efficient batch processing of transactions through a Chrome extension. By integrating dApps within iframes in the Console, it utilizes the Brahma Console's Safe wallet for smooth interactions.
Connect is particularly beneficial for power users and protocols, streamlining their transaction routines and enhancing efficiency.
Is Brahma Connect available on all networks?
Initially, Brahma Connect is accessible on Blast, but shortly after its release, it will also be available on Arbitrum and Ethereum mainnet.
Why should I choose Brahma for interacting with dApps?
Brahma Connect simplifies the process of navigating dApps on Console by allowing users to run sequential strategies across multiple protocols. It enables users to batch multiple transactions into a single transaction, thereby saving time and reducing gas costs.
Brahma Connect enables users to navigate across multiple dApp frontends, build sequential batches of transactions, and utilize the RPC Manager to import the final state of previous transactions into subsequent ones.
Which browsers does the extension work with?
The Brahma Connect extension seamlessly functions with Chrome and browsers built on the Chromium framework, including Brave. This compatibility offers users flexibility in their choice of browser. Here’s your onboarding guide to get started.
Is Connect secure and what does it entail?
Yes, Brahma Connect prioritizes security by eliminating the need for private key management within the extension. This ensures that users maintain full control over their assets. It utilizes a forked node and Chrome runtime for secure communication with dApps, enabling safe transaction previews and simulations.
Which dApps can I use with Connect on Blast?
Brahma Connect is compatible with dApps that support smart contract wallets and avoid wallet signature schemes. The following dApps are operating smoothly with Connect on Blast, with upcoming support on more: Juice Finance, Ambient Finance, Mangrove Exchange, Baseline, Orbit Lending, Bladeswap, ZeroLend, Synapse, Synfutures and Hyperlock Finance among others.
What if a dApp is unsupported?
Brahma Connect currently does not support dApps that require personal signing, support injected wallets, or use off-chain APIs instead of an RPC.
If a dApp is unsupported, Brahma Connect directs users to Wallet Connect as an alternative method. It progressively tests dApps for compatibility, providing guidance within the Connect iframe for each individual dApp.
Why does it need a separate browser extension?
The Brahma Connect extension leverages Chrome's secure runtime and declarativeNetRequest API to efficiently monitor and manipulate RPC requests. This integration enables a unique simulation mode within the Console, optimizing transaction execution and enhancing interaction with dApps. Further details on the API can be found here.
Community
Last updated