jakiro
Author: Francesco Translation: Shan Ouba, Bitchain Vision
Just like the browser in the Internet, the user interaction layer in the encryption world, it helps users navigate and encrypted and interact with decentralized applications (DAPP).However, a tricky problem is emerging:
Although the encryption protocols and DAPP have been evolved, the tools of users interact with them are slow.With the approval of ETF and the development of cryptocurrencies into the field of cross -chain DEFI, these tools are facing new challenges, such as more deeper institutions to participate in DEFI and new cross -chain income opportunities.
>
The current encrypted wallet can only provide a single perspective, which limits the potential of users to explore encryption and DEFI, just like the first graphical user interface browser MOSAIC. It is just a way to provide users with simple access to the Internet.
>
From the outside, most wallets look similar: browser extensions with limited features.
>
However, with the increasing complexity of encrypted user groups, most wallets cannot meet increasing demand, such as handling complex trading sets, user intentions, DAPP intention or security requirements, and usually do not support the most important feature of cryptocurrencies: Yes, yesProgramming.
As the encrypted world becomes more and more complicated, traditional wallets are difficult to meet user needs, and users need better tools.Brahma, as a chain interactive layer, stands out for investors who are not just traded but actively participating in the chain activities.
>
Console’s beauty is that it isDo not compete with other wallets
We believe that in the encrypted world, each type of users has a suitable solution:
Retail users: They will always use the EOA wallet (such as Rabby, Metamask) to connect DAPP, perform rapid transactions and store their assets in cold wallets.EOA is the initial contact point of any users entering the encryption field. They use a “one -size -fits -all” method. Most EOA features are similar, only slight differences.However, EOA and DAPP interaction are not the safest way.They are not programmed and cannot judge the intention of users or DAPP.
Institutional user: They will always use multi -party computing (MPC) wallets for simple transactions.MPC is similar to EOA, but does not require users to store seeds or private keys.They usually face institutions and high net worth people, focusing on hosting and security rather than execution.Therefore, they are expensive, not everyone can afford it, and lacks any programming.Due to these characteristics, the active operation of MPC may be costly at a high price, and it needs to trust the company that manages the wallet.
Safe Wallet (Safe, Avocadowallet): They are programmable smart contracts, without the private key owned by EOA wallets.The smart wallet also has multiple signature functions, which increases additional security, including internal trading simulator, allowing users to view what is doing in the language that can be read in humans.However, these wallets are more complicated, and not all encrypted users understand their functions.Therefore, their user experience is relatively awkward.
The good news is that all these wallets can be emphasized through Console. Console provides users with additional security, automation and execution tools, thereby improving the efficiency and productivity of the operation on the chain.Therefore, Console is based on Safe. It is one of the most mature custody solutions in the industry, and its contract protection assets exceed 80 billion US dollars.
Where does Console play a role?
Console is the next evolutionary step after wallet: it is an interactive layer on the chain that allows users to seamlessly navigate and operate between DAPP and protocols.Console has inherited the advantages of EOA, smart wallets and MPCs, and aims to become a “base camp” for all investors on the chain to seek beyond the function of wallet.
For this reason, Console focuses on:
-
Security
-
Programmable
-
Improve user experience
-
Efficiency and productivity
It can be said that the main difference between Brahma is that it “takes care of the hosting” rather than “transaction first” to ensure that users benefit from the highest level of security.
What pain points are solved?
· Team collaboration and professional user design: Currently lacks tools designed for teamwork and efficiency improvement.Console created the perfect environment of teamwork to improve the efficiency of operating processes, team collaboration and transaction execution.
· Risk isolation and authorization on the chain: Authorization is never so simple.Console improves your or team’s operation methods on the chain.Divide risks through sub -accounts, avoid capital loss, and easily allocate operations to define the permissions of each sub -account.
· Programming: Brahma is an interactive layer connecting other DAPPs and protocols.Brahma users can use risk isolation, authorization and automation to enhance programming, and completely change their DEFI workflow (for example, AAVE’s loan automation function can automatically re -balance and manage positions, DCA, TWAP strategies, etc.).
· Console implementation can be combined: users can use API to add any support DAPP to their workflow.
· Native visits to block -based summary DEFI indicators and information, so that the Debank and Defillama information can be operated and integrated into an automated routine (using a chain and under -chain trigger).
· Guarantee safety and autonomous custody: New infrastructure is usually vulnerable to attack and is usually not suitable for large transactions.Therefore, Brahma always guarantees 100% independent custody and allows users to introduce existing SAFE to reduce friction and make the process no need to trust.
· Human readable changes: Console understands user intentions and DAPP intentions, which can show the code that can be readable according to the operation.In addition, Console allows developers to use our technical stack to create new strategies and automation, develop new use cases and native functions, so that Safe can use large -scale use.
Console can be compared to “DEFI’s ambiguity”. It is the boundary between user interaction and continuously broaden the boundary of user efficiency and productivity on the chain.
>
