Many people think that chain abstraction is a concept concocted by VCs, but it really isn't. I was deeply inspired after reading SevenX's article describing the future of chain abstraction. The current market's highly competitive fields such as high-performance layer1, parallel EVM, Layer2 RaaS, layer3 application chains, and cross-chain environments have made modularization and chain abstraction two derivative twin narratives. In my opinion, when "modularization" reaches a certain level, "chain abstraction" becomes necessary. Next, I will elaborate on my views:

1) The competition in the current layer1 public chain layer is intense. In the previous round, everyone tended towards EVMization, resulting in the emergence of many EVM-compatible layer1 chains. This round, the inherent shortcomings of EVM have been criticized, leading to the emergence of high-performance layer1 chains that focus on parallel transactions, such as Solana, Sui, Aptos, as well as parallel EVM chains with completely restructured underlying architectures, such as Monad, Artela, etc.

2) The narrative of layer2 is no longer dominated by pure EVM. The BTC layer2 ecosystem has emerged, with EVM-compatible types of layer2 like BSquare, as well as UTXO homomorphic binding types of layer2 like CKB. In addition, highly modularized combined layer2 ecosystems have also emerged, such as Celestia with modularized DA layer design, and Eclipse using Solana VM as the execution layer, and so on.

The more of these chains there are, the more intense the competition becomes, and the interoperability issues between chains become more prominent, involving at least: heterogeneity in underlying languages, account models, contract standards, etc.

For example, the differences between the Move, Rust, and Solidity languages result in high learning costs for developers. The differences in account and state models make it difficult for Ethereum's EOA accounts to be compatible with Bitcoin's UTXO model. The differences in smart contract standards between different chains, such as ERC20, ERC721, etc., are not easily handled in Object-centric chains based on the Move system. There are also significant challenges in Relay relays' atomic communication interaction between different chains, requiring real-time monitoring of contract states on each chain and coordination for sequential execution through RPC. In addition, there are differences in consensus verification mechanisms (POW VS POS), governance coordination mechanisms, scalability capabilities, underlying security trustworthiness, and so on.

The complex factors behind these chain-centric issues directly lead to many poor user experience problems:

1) In EVM and non-EVM full-chain environments, users have non-uniform account addresses.

2) There are inconsistent signature specifications for controlling EOA addresses, smart contract addresses, and MPC management, requiring signature aggregation.

3) Users require different gas fee standards in different chain environments, leading to challenges in gas conversion and friction.

4) There are different liquidity depths between different chains, and users do not have a unified liquidity management environment, etc.

Faced with the compatibility challenges between various chains, the goal of chain abstraction is to hide these technical complexities behind the scenes, and present users with a simple front-end UX interface. Everyone is familiar with @ParticleNtwrk's efforts to allow users to directly connect to the EVM environment through Unisat, which led to the introduction of BTC Connect. In fact, this is only a small part of the grand project of chain abstraction. In addition to this, what other behind-the-scenes technical integration operations has Particle done for chain abstraction?

1) Building a modular L1 public chain underlying architecture based on the Cosmos SDK, so that Particle can connect to EVM environments, BTC UTXO environments, Solana high-concurrency environments, etc. Cosmos's IBC and relays provide the framework prerequisites for its maximum connection to complex multi-layer1 environments.

2) Building a Keystore contract to achieve full-chain account abstraction, where the contract manages users' account and state information on various heterogeneous chains, including addresses, public keys, signatures, cross-chain message transmission, etc.

3) Using decentralized Bundler services, i.e. intent Solver processing centers, to receive complex user operation instructions and convert them into executable transactions on the chain, such as Paymaster for gas payment, Social Recovery, etc., all achieved through UserOps built on the intent layer to optimize the transaction experience.

4) Cross-chain communication and relayer to be responsible for listening to transactions and state updates on various chains, and responding and providing feedback in real-time in sequence, providing the foundation for a smooth full-chain interaction experience and unified liquidity experience.

5) To address the issue of non-uniform Gas Tokens, Particle will also issue the ecosystem token $PARTI in the future to unify gas consumption on different chains, achieving gas abstraction. Importantly, in addition to cross-chain asset settlement, Gas Tokens will also provide a dual-pledge security model mechanism to ensure the trust and security of interactions on various chains.

Recently, MerlinChain TGE, which integrates Particle's account abstraction and BTC Connect services, has gone online. I noticed that there have been some complaints in the market about the poor user experience. In fact, it is not difficult to understand. The chain abstraction service provided by the main body is equivalent to a plug-and-play interface extension service. The optimization and adaptation of the interface itself (CDK) are also crucial. Over 60 chains, such as Bearchain and opBNB, have also integrated this service. Particle only provides a standardized chain abstraction service that can be directly integrated by cooperative projects. It is not realistic to single-handedly address all compatibility and user experience issues.

In my opinion, Particle is a typical modularized layer1 public chain dedicated to solving the complex problems of chain abstraction. SevenX also cited different solutions in the article, such as @LightDotSo and @NEARProtocol, but I won't go into detail about them. Understanding these types of technical services is not difficult.

The essence of chain abstraction is "connection integration" and "heterogeneous compatibility", with the effort being behind the scenes, allowing project developers to quickly and cost-effectively integrate and apply mature extension services, and enabling users to perceive a seamless interactive user experience.

In short, the future of the chain abstraction field is shaped by the complexity of the current cross-chain native environment. At present, everyone is still immersed in the irrational period of complexity and prosperity brought about by modularized combinations, and may not yet perceive the value of chain abstraction. When the vision of Mass Adoption is gradually realized, and the competition between chains intensifies to the point where a shakeout is needed, the value of the chain abstraction field will naturally become apparent.

免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。