Elfa retires Trade and its balance view

Elfa retires its Trade interface

Elfa scheduled its Trade page and wallet-balance display to close on September 10, 2026 at 06:00 UTC. It says assets remain on-chain and can be accessed through a compatible wallet using the account’s exported credentials. The notice offers transfer and wallet-export routes. The deadline has passed; this article explains the transition, not an active trading feature.

A wallet interface is different from the account

Ethereum’s wallet documentation provides a useful explanation of the underlying distinction: a wallet application is a tool for viewing and interacting with an account. The account is identified by an address, while the private key authorises actions. Changing the application used to access an account is therefore conceptually different from sending assets to another account.

This is Ethereum-specific background, not confirmation that every wallet supports every asset previously visible in Elfa. Compatibility still needs to match the actual network and account. The explanation helps readers understand why a disappearing balance screen is not, by itself, evidence that the underlying assets disappeared. It also explains why an account credential must be treated differently from an ordinary username or public receiving address.

Distinguish importing access from making a transfer

Imagine a fictional account A holding an asset. Opening account A through another compatible interface changes the tool used to view and control it. Sending the asset from account A to a new account B is a different operation: the destination changes. These two tasks need different evidence of completion.

For the first, a person would want to establish that the intended account and network are visible and usable in the new interface. For the second, the person would need the resulting transfer record and receipt at the intended destination. Seeing a familiar balance in a new application should not be described as proof that a transfer took place if none was sent.

This example explains the terminology; it is not a recommendation to import a secret into an arbitrary app. The appropriate route depends on the exact account, network and compatible software. Follow the provider’s official transition instructions and the receiving wallet’s own documentation for that setup.

Build a precise record before asking for help

A useful support question identifies what the person is trying to do and where the process stops. For example: the balance screen is no longer present; an export control cannot be located; or a chosen wallet does not show the expected network. Those are different problems. A general statement that funds are “stuck” gives much less information.

The record can include the public account address, network, expected asset and relevant transaction reference. It should not include the private key or recovery phrase. A person can explain that an export was attempted without pasting the exported secret into a chat or ticket. That distinction allows a legitimate support discussion to remain useful without sharing the authority over the account.

For an unexpected message offering to perform the migration, independently verify the route through the published notice. An unsolicited helper’s confidence is not evidence that they should receive account credentials. A service transition can create urgency, so it is particularly useful to separate a request for information from permission to control funds.

What a completed transition should mean to the user

Our suggested completion check is practical: the person knows which account they are using, which network holds the expected asset, which interface can access it and what evidence confirms the result. A new app icon or a successful login alone does not establish all of those facts.

If something remains uncertain, keep the uncertainty specific. It may be an unsupported token display, the wrong network selection or an unresolved export step; those possibilities should be investigated rather than assumed. The aim is to identify the missing part of the workflow without repeatedly taking irreversible actions.

For someone with assets to manage, the immediate concern is continuity of access. Understanding the account, the interface and the difference between a transfer and an import makes the official transition notice much easier to apply correctly.