Brahma Console | Now Live on Blast
Mar 7, 2024
3 min
Welcome to another issue of our monthly recap!In a leap year, February has come as a month full of updates. Let’s get started.
We officially launched on Blast Mainnet from day one. Console is the best way for users and protocols to interact with the Blast ecosystem.
Lastly, we’re about to launch our Liquid Restaking Tokens (LRTs) automation.
It will allow users to automatically set a depeg % that automatically triggers an emergency exit in case of a systemic depeg of LRTs. This is how the automation works under the hood:
We monitor the price deviation between the Balancer pool and the desired LRT vault. When the deviation reaches the trigger percentage, the LRT is exchanged for the underlying asset(ETH) and transferred to the main account.
As the extend of the risks of LRT tokens are not clear yet, users who might want to protect themselves against the depeg of their assets can do so automatically on Console.
For our initial launch we will be live on mainnet and support Renzo and EtherFi, with more LRT providers to be integrated soon.
For more information on Brahma Console and our upcoming features, make sure to follow us on Twitter and try Console on Blast to benefit from multiple layers of rewards: https://www.brahma.fi/blast
What’s next?
During the next couple of week we’ll release Sub-Accounts and Policies on Blast, allowing users to segregate risk and improve multisig coordination for teams via the creation of different Sub-Accounts with lower threshold executions. Furthermore, users will be able to specify and limit what each Sub-Account can do using Policies, ensuring trustless delegation of operations with no need for monitoring.
We’re also incredibly excited for the launch of Console Kernel, which allows chained execution on Console. Kernel is a Chrome extension providing an alternative to WC to interact with dApps from Console.
Thanks to Brahma Console Kernel, users will be able to build sequential batches of transactions by navigating through multiple dApp frontends. Our custom RPC manager will keep track of the state and carry it on for the next transaction.
Then, they can simulate and execute the whole batch in one transaction. This comes especially handy to protocols and users (e.g., options protocols) with many transactions to execute in a row.
No need to execute transactions individually — with Kernel, you can just batch them up and greatly improve your user experience.