> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/products/cash/account-upgrade.md).
# Account upgrade
As a planned extension of ether.fi Cash, the core chain for Cash is updating in Apr 2026
## Universal cross-chain addresses
Ether.fi has, since the launch of ether.fi Cash, provided a cross-chain deposit service utilising universal addresses. Within this architecture, each user is assigned a universally consistent address across multiple EVM-compatible blockchains ('top-up' chains). One of these addresses is designated the 'core' chain, and any supported assets deposited on any of the supported top-up chains are transparently bridged to the core chain. Refer to our [technical documentation](https://etherfi.gitbook.io/etherfi/cash/technical-documentation#id-2.-effortless-cross-chain-via-universal-address) for more information.
The core chain is the network that holds user assets after bridging, and is the network on which all card payments are settled, and on which swaps and other actions take place.
## Account upgrade process
The account upgrade process leverages the existing cross-chain address architecture. For each existing user safe on the current core chain, a safe is deployed on the new core chain (Optimism), and a migrate function is called. This results in the cross-chain deposit service treating the previous core chain as a top-up chain.
### Addition of a new core chain
The upgrade process is driven by the addition of a new core chain, and switching the existing core chain to be a supported top-up chain. Throughout the upgrade, all assets exist on the universal safe address, or in the bridges used.
The following existing bridges are used, and live on-chain tracking is available for all:
* Layer zero
* Stargate
* Canonical L2 bridges
The end result is that all assets arrive on the new core chain, and all current functionality and custody behave exactly the same.
## Full multi-chain vault support
This upgrade, which allows switching of core chains, sets the groundwork for enabling a fully non-custodial chain-agnostic vault system where users can arbitrarily bridge assets between multiple core networks to enable native DeFi integrations. An example of this would be a HyperLiquid trading integration where user assets can exist across 2 networks concurrently and be used for card spending or trading within the same non-custodial architecture.
Multi-chain vault support will be a future upgrade.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://etherfi.gitbook.io/etherfi/products/cash/account-upgrade.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
