Ethereum developers presented a new technical proposal that aims to resolve account fragmentation between networks. This is the standard ERC-8092: Associated Accounts (Associated accounts).
This standard postulates a common method for linking addresses that exist in different chains and that even They use different cryptographic architectures:
By leveraging ERC-7930 for address representation, ERC-8092 enables associations between accounts on different chains and with different cryptographic architectures. This cross-chain capability is essential for modern multi-network identity systems.
ERC-8092 document
In technical terms, ERC-7930 is a complementary standard that defines a common format for describing addresses of different networks, without establishing relationships between them.
On that basis, ERC-8092 build a mechanism to associate accounts that can exist on multiple chainsbeyond Ethereum. It is an identity layer that aims to be compatible with heterogeneous architectures.
However, both proposals are in a state of review and, to achieve what they promise, they must be approved by the Ethereum community.
What problem does ERC-8092 solve?
ERC-8092, presented on December 2, was created to associate accounts from different networks without the need for move funds or deploy contracts specific.
The text of the standard clarifies the problem it addresses:
Managing multiple blockchain addresses on different chains and platforms creates friction for both users and applications.
ERC-8092 document.
To address that problem, ERC-8092 proposes a common infrastructure that allows:
- Establish subaccount relationshipslinking multiple addresses under one main identity.
- Delegate actions between accountsenabling one address to act on behalf of another explicitly.
- Add reputationconsolidating history and credentials distributed between different addresses.
- Connect identities across networksallowing associations between accounts that exist on different blockchains.
A possible use in real life
In practice, a user can divide their activity across several wallets.
One for custody, another for interacting with applications, another for signing messages, another for payments and another focused on privacy. Although this separation is common, applications do not have a standard way of recognizing it.
With ERC-8092, the user could declare which accounts are associated. An application, upon detecting that link, could recognize actions carried out from another address without asking for additional steps.
This process, as explained, would occur without moving funds or exposing balances, and with the possibility of revoking the relationship at any time.
Possible disadvantages of using “multichain accounts”
Those types of partnerships could also pose challenges.
The possibility of linking multiple addresses under the same identity increases the risk of correlation between accounts that today remain separate, which could affect privacy if the applications or third parties access that information indiscriminately.
Furthermore, poor management of permits or delegations could amplify the impact of operational errors or security compromisesby extending its effects to more than one associated account.
However, the design of ERC-8092 includes mechanisms that help mitigate these risks.
For example, associations can be stored on chain or off chain. On-chain storage prioritizes transparency and composability, while off-chain storage aims to reduce costs and improve scalability, in addition to allowing the user limits public exposure of links between their accounts.
Additionally, any of the associated accounts can revoke the association at any time.
The standard defines rules to validate dates, verify signatures and check if a link is still validreducing the impact of outdated associations, configuration errors, or delegations that you no longer want to keep active.
How does the proposed ERC-8092 standard work on Ethereum?
ERC-8092 defines two core data structures. The first is the Associated Account Record (AAR).
It details which account initiates the association, which one approves it, when it is valid and, optionally, in what context it is used.
The second is the Signed Association Record (SAR). This wraps the AAR with the cryptographic signatures of the associated accountsthe type of key used and the link revocation status.
Both accounts sign the same structured message using EIP-712, an Ethereum standard that defines how to sign readable and verifiable data. The result is a crypto proof without intermediarieswhich can be validated by any application.
According to its document, ERC-8092 supports multiple transaction signing schemes:
- Ed25519 (common on networks like Solana).
- BLS12-381 along with methods that enable the use of passkeys and biometric authentication.
Collectively, ERC-8092 seeks to provide a common technical framework for declaring, verifying and managing associations between accounts, with the goal of facilitating the development of multi-chain identities.