The transformation from externally owned accounts to smart contract accounts has a strong momentum and has been supported by many core entrepreneurs, including others. However, the adoption is not as extensive as that. The main problems include the difficulty of migration caused by the bear market, the high cost of signature and the most critical development problem. The most obvious advantage of account abstraction is that it can use code customization functions, but the non-interoperability of functions brings major challenges, which will hinder the collection. In addition, it is also an important challenge to ensure security while being scalable and composable. The emergence of modular account abstraction is a subdivision in the development trend. This innovative method can separate smart accounts from their custom functions, and its goal is to create a modular structure to develop wallets with diverse functions, security and seamless integration. In the future, modular account abstraction can realize a free smart contract account application store to make wallets and focus on improvement. User experience does not need to spend too much energy on building functions. In the process of people's contact with blockchain, the traditional account abstraction has brought many challenges, such as mnemonic fees, cross-chain operations and multiple transactions. The use of smart contract accounts allows programmable verification and execution, which means that users will be able to approve a series of transactions at one time without signing and broadcasting each transaction. Account abstraction can also achieve more functions, such as improving user experience, abstraction and session keys to reduce costs. Such as batch transactions and improving security such as social recovery, there are two ways to achieve account abstraction. At present, some protocols themselves provide local account abstraction support. Transactions are supported by a single memory pool and transaction process, and all accounts have been removed, and they have local smart contracts like this. The wallet contract layer has introduced a separate one for Ethereum and the like to support things like peace without changing the consensus layer. The dilemma of building infrastructure and being built and adopted, the topic of account abstraction has been discussed since, and it has been further promoted to people's attention this year. However, the number of deployed smart contract accounts is still far less than that for us to deeply study the impact of this dilemma bear market. Despite the advantages such as seamless login and abstraction, in the current bear market, all users are educated users and there are not many new users, so there is no incentive to adopt wallets. In this way, some leading companies are gradually adopting, for example, by introducing their systems and no solutions, which has driven about 10 thousand transactions in just one month. For wallets and applications that have accumulated users and assets, it is still a challenge to migrate assets safely and conveniently, but a scheme like this can allow a one-time migration transaction signature problem. The smart contract itself cannot sign the message because it has no similar attempt as that private key, but the message signature is in the first place. This transaction didn't work before, which challenges the use of counterfactual deployment wallet. The successor who is backward-compatible may be able to solve the previous problems. Compared with the standard, the deployment of simulation and execution will produce higher costs, which has also become one of the obstacles to adoption. However, some tests have been carried out, such as separating account creation from user operation to eliminate engineering problems related to an account. The team has established a basic implementation for developers. However, with Developers will face more challenges when they expand to more detailed and specific functions for different use cases. In this paper, we will discuss the engineering problems in depth, and solve the engineering problems through modular intelligent contract accounts. The engineering problems can be further elaborated in three aspects: fragmentation, security and scalability. Fragmentation can now enable functions in many ways, whether through specific or independent plug-in systems. Every platform and service provider will follow their own standards to urge developers. Deciding which platforms and service providers to support may lead to potential platform vendor lock-in or redundant work security. Although the decoupling of accounts and functions brings flexibility advantages, it may also make security problems more serious, because all functions may be audited together and lack of independent evaluation may increase the risk of account vulnerabilities. Scalability is very important to maintain the ability to add, replace or delete functions with the development of accounts. Every update of existing functions will introduce complexity in order to cope with it. To solve these problems, we need scalable contracts to ensure the safe and efficient upgrading of reusable cores, to improve the overall development efficiency and standardized interfaces to ensure the smooth transition of contract accounts between different front-ends. These terms converge on a common concept and build a modular account abstraction architecture. Modular account abstraction is a subdivision of extensive development. It envisages modularization of smart accounts to provide customized services to users and enable developers to minimize. However, it is a great challenge to establish and promote new standards in any industry. Before everyone accepts the same standard, there may be many different solutions in the initial stage. It is encouraging to see those people who are committed to improving and promoting account abstraction, whether they are wallet infrastructure teams or protocol layer designers, who are working together to speed up this process. Modular structure, how to call modules for master accounts and modular accounts, and how to realize function delegation and generation. Manage contract external call and delegate call. Although delegate call is similar to call, it is not executed in the target contract but in the current state of the calling contract. This means that any state change made by the target contract will change the storage agent contract and delegate call of the calling contract. To realize the combinable and scalable structure, it is necessary to introduce a basic concept: agent contract, agent contract, whose logic and state can not be updated after deployment, but the agent contract can be used. Delegated call is deployed to another contract, and it is executed in the current state of the proxy contract by referencing the implementation function. Use case Although the proxy contract remains unchanged, you can deploy a new implementation behind the proxy contract, which is scalable and has lower deployment and maintenance costs on the public blockchain. Architecture What is the leading modular smart account infrastructure? It aims to provide security and flexibility that has been tested in actual combat. It enables developers to create diverse applications and wallets. Many teams are building applications based on or inspired by it, for example, using native and when launching their smart contract accounts. 比特币今日价格行情网_okx交易所app_永续合约_比特币怎么买卖交易_虚拟币交易所平台

注册有任何问题请添加 微信：MVIP619 拉你进入群

文章转载注明 网址：https://netpsp.com/?id=63202