Chain abstraction

Chain abstraction is a design goal more than a single technology. The user sees one balance and one account, and when they act, the wallet or app works out behind the scenes which chains hold the funds, which network the app lives on, how to bridge, and how to pay gas. Intents and solvers, account abstraction, cross-chain messaging and unified account systems are the building blocks.

It responds to the fragmentation created by dozens of L1s and L2s, where users often hold the right token on the wrong chain. Wallets, payment apps and infrastructure projects market chain-abstracted experiences, and standards such as ERC-7683 for cross-chain intents aim to let different providers interoperate instead of building walled gardens.

Hiding complexity does not remove it. The user still bears bridge and solver risk, fees are less visible, and a failure in one leg can leave funds stranded on an unexpected chain. Different vendors use the label for very different architectures, some largely custodial, so it is worth asking who actually holds the assets in transit.