Although this may be a bit exaggerated, the speed of application innovation may not be as fast as the speed of new public chain additions.
Especially recently, with the improvement of modular public chains and RaaS, the "scenario chain" has been rapidly developed. For example, DePIN, AI or financial applications require an independent blockchain network, and many financial or comprehensive institutions also need to issue their own chains (HashKey Chain and Base).
In addition, Bitcoin's second layer has also been launched intensively in the past two months, such as Citrea, BOB, Bitlayer, Merlin Chain, etc. Finally, there is the eternal topic of "performance", which is also driven by parallel virtual machines (and Parallel EVM), such as Monad, MegaETH, Artela, etc.
For ordinary users, managing assets and applications on multiple chains has become increasingly painful, not to mention that they have to reserve some Gas (transaction fees) on each chain in case of emergency.
These problems have been solved in the past few years with the popularization of "cross-chain bridges", which have partially solved the liquidity problems and are sometimes classified under the topic of "interoperability". However, how to bring these liquidity together or connect all these experiences in series is a milestone.
This is how this new concept and narrative of “chain abstraction” was born. It can also be seen as “interoperability 2.0” or the ultimate form of such products.
Three options
Because of these experience problems, the interoperability of blockchains has become increasingly important. However, the purpose of users is not to use a "cross-chain bridge", but to achieve more specific needs, such as trading specific assets or using certain applications.
In a scenario with only a few chains, users can barely manage cross-chain bridges and multi-chain assets by themselves. However, with so many chains competing in the future, and the decentralization of applications and liquidity, it is completely unrealistic for users to safely manage these assets by themselves. Such feedback is often heard in the community: "I have completely forgotten what assets I have pledged on which chains and which protocols."
Users don’t want to know what “chain” is, they just want to know what it can be used for. Therefore, “demand” should be what users need to know, and hiding “chain” under demand is a normal user’s cognition.
Precisely because cross-chain bridges cannot solve the needs of users to uniformly manage assets and directly use applications, the concept of chain abstraction was proposed as another important node under the topic of "interoperability".
There are already many teams focusing on "chain abstraction" and providing solutions, but overall, each team has similar modules and architectures, but their respective focuses vary greatly. They can at least be divided into the three most representative directions: signature network, universal account layer, and cross-chain bridge aggregation.
In fact, it is also easy to understand. For chain abstraction solutions, users are usually required to have a unified account. This account and associated accounts can submit transactions on multiple chains, while solving problems such as gas payment and cross-chain information communication. In addition to the above common parts, these solutions focus on different independent modules due to their own characteristics.
NEAR focuses on building a decentralized network with MPC nodes to achieve multi-chain signatures, while Particle is more focused on the EVM ecosystem, first supporting the public chain ecosystem that is currently more widely built based on the EVM technology stack. Other solutions like Polygon and Optimism are more focused on a unified cross-chain bridge and their own RaaS ecosystem, only serving L2 using CDK or OP Stack.
Signature Network: NEAR
The signature network solution was proposed by NEAR and is called "Chain Signatures". The core of this technology is to allow the address generated on the NEAR chain to become the user's main account, while the accounts and transactions of other chains are signed through a decentralized multi-party computing (MPC) network and submitted to the target chain.
In addition, NEAR has launched a module called Multichain Gas Relayer. The main function of this module is to pay the gas fees of transactions, solving the problem that users need to hold native tokens on each chain when conducting cross-chain transactions. Currently, this function supports using NEAR or NEP-141 tokens on NEAR to pay gas fees, and cannot support a wider range of gas abstractions.
The fundamental reason for this design is that NEAR is not an EVM-compatible chain, but as we all know, the mainstream of the market is still EVM-isomorphic chains, which are much more numerous. Therefore, interoperability with EVM-isomorphic chains can only be achieved through the MPC network.
This will also bring some experience-level problems:
High migration cost: For users of the Ethereum ecosystem, it is impossible to migrate to the NEAR ecosystem directly (for example, using MetaMask), and they still need to create a new account through NEAR.
The transaction confirmation process is long: Because the EVM multi-chain wallet created by NEAR is EOA (that is, a wallet generated by public and private keys), for cross-chain transactions that require multiple transactions (at least authorization + transaction) to be queued and signed in parallel, the user may need to wait for a long time for confirmation. And because it is separated into multiple transactions, all the gas consumed cannot be optimized.
From the perspective of token utility, NEAR's native token will become the Gas token for the entire chain abstraction process. Users need to consume NEAR to pay all Gas costs in the entire chain abstraction process.
General Account: Particle Network
The Particle Network solution focuses more on the account itself, scheduling the status and assets on other chains through an independent blockchain network. To put it more bluntly, users only need to use the Particle Network address to access the assets and applications of all chains. Particle calls this address the Universal Account.
As for the relay of information, that is, the transmission of messages across different chains, Particle's L1 monitors the execution of UserOps of the external chain through the Relayer Node on its own chain. However, since the underlying layer is still based on EVM, if it is to support the addresses of non-EVM isomorphic chains, other modules may be required to support it, such as an MPC network similar to NEAR.
So this is a big difference. Unlike NEAR, Particle Network is designed with EVM as the top priority. It is natively an EVM address, and it is quite easy to access any chain, application, or wallet in the EVM ecosystem.
From a user's perspective, Particle Network's EVM-first solution allows users to easily migrate accounts previously created in the EVM ecosystem, which is just a matter of adding a network in MetaMask, which is as simple as adding the Optimism or Arbitrum network at the time.
Take a scenario that heavy or Web 2.5 users will have a strong sense of as an example: USDT is distributed on several chains, for example, 100 USDT on chain A, 100 USDT on chain B, and 100 USDT on chain C. When users want to use these assets to purchase assets on chain D, it will be very troublesome. Although these USDTs are completely owned by users, the user experience cannot be conveniently implemented because these assets are separated. If all these USDTs are moved to one chain, it is not only a matter of finding a cross-chain bridge and waiting time, but also possible to prepare Gas for different chains. The Universal Account provided by Particle L1 allows users to pool purchasing power distributed on different chains, purchase assets on any chain with one click, and can choose any Token as Gas. The underlying operating mechanism can be referred to in the figure below.
In addition, the biggest difference between the Particle solution and NEAR is that the granularity of transactions is different, and batch signatures and transactions can also be achieved through aggregation. That is, users can bundle multiple transactions together, which not only saves the number and time of user signatures, but also saves the Gas involved in complex transaction scenarios.
Particle has designed a variety of consumption and usage scenarios for its token $PARTI. As an ordinary user, the most direct use is to use it as a Gas token for Universal Account to complete transactions on any blockchain. If you don’t have $PARTI, you can also choose other tokens to pay for it (but no matter which token is used to pay for Gas, $PARTI will be consumed). For the entire ecosystem, Particle L1 has 5 node roles (see the figure below). You can become a node by staking $PARTI and participate in network consensus and transactions to get more rewards. In addition, $PARTI tokens can also act as LP tokens in the Particle Network, participate in cross-chain atomic exchanges and earn transaction income.
Cross-chain bridge aggregation: Polygon AggLayer
Two typical cross-chain bridge aggregation solutions are Polygon AggLayer and Optimism's Superchain. They are also designed with the Ethereum ecosystem as the priority.
Compared with traditional cross-chain bridges, AggLayer hopes to unify the standards of cross-chain bridge contracts, so that each chain and Ethereum do not need to have independent smart contracts. Therefore, in this solution, the Ethereum mainnet is the center of everything, and then a zero-knowledge proof aggregates the cross-chain information of all chains.
But the problem here is that other chains may not accept this unified liquidity cross-chain bridge contract, which will bring some resistance to accessing new public chains, unless this solution can be accepted by all other public chains or become a widespread industry standard. If you understand it from another perspective, AggLayer is actually an additional function for teams that use Polygon CDK to develop chains, so those who do not use CDK will not have this function built-in.
Optimism's Superchain is somewhat similar. They will first focus on the interoperability between Ethereum Layer2. After all, some teams have used OP Stack to develop more second-layer networks. They can use this method to achieve interoperability, but what is more important is how to expand to a wider range of other public chain networks.
So from the user experience point of view, AggLayer and Superchain can be easily migrated from MetaMask because they are bound to the EVM ecosystem. However, they cannot be accessed from ecosystems outside of EVM.
Summarize
Although these solutions differ in their focus, their common goal is the same: to provide users with a simple and intuitive way to manage multi-chain assets and applications in a world where blockchain networks are rapidly expanding. Each team is working hard to solve how to keep operations simple and clear for users in a multi-chain environment.
From the three solutions, NEAR's signature network is centered on the NEAR network, and is designed to implement cross-chain signatures in a decentralized MPC network. Particle Network's universal account focuses on enhancing interoperability through the powerful ecosystem of EVM, while being able to access more other public chain ecosystems. Polygon AggLayer focuses on optimizing interoperability within the Ethereum ecosystem by aggregating cross-chain bridges. Although these solutions have different technical implementations and application focuses, they all aim to improve the convenience and reduce complexity of users' cross-chain operations.
But I think that in the end, these technology choices will all lead to the same end. Because they all face the same ultimate goal - to improve the user-friendliness and interoperability of the blockchain ecosystem. With the development of technology and further integration of the industry, we may see more cooperation and integration, and the boundaries between various solutions may become blurred. So now it is more important not only to choose technology and narrative, but also to implement it as soon as possible and let users perceive this new experience of full-chain aggregation.
Reference Documents:
https://pages.near.org/blog/chain-signatures-launch-to-enable-transactions-on-any-blockchain-from-a-near-account/
https://blog.particle.network/chain-abstraction-landscape-report/
https://blog.particle.network/particle-network-modular-l1-chain-abstraction-announcement/
https://polygon.technology/blog/aggregated-blockchains-a-new-thesis
