Ethereum developers have announced a new technology proposal aimed at solving account fragmentation across networks. this is the standard ERC-8092: Related accounts (associated account).
This standard assumes a common way to link addresses that reside on different chains. These use different encryption architectures.
ERC-8092 leverages ERC-7930 for address representation, allowing accounts on different chains to be associated with different cryptographic architectures. This cross-chain capability is essential for modern multi-network identity systems.
ERC-8092 documentation
Technically speaking, ERC-7930 is a complementary standard that defines a common format for writing addresses for various networks. without building a relationship between them.
Based on this, ERC-8092 Associate accounts that can exist on multiple chainsBeyond Ethereum. This is an identity layer intended for compatibility with heterogeneous architectures.
However, both proposals are under consideration and must be approved by the Ethereum community to fulfill their promises.
What problem does ERC-8092 solve?
ERC-8092, announced on December 2nd, was created to link accounts from different networks without need Move or deploy funds contract specific.
The text of this standard clarifies the issues that the standard addresses.
Managing multiple blockchain addresses on different chains and platforms creates friction for both users and applications.
ERC-8092 documentation.
To address this issue, ERC-8092 proposes a common infrastructure that allows:
- Establish subaccount relationshipslink multiple addresses under one primary ID.
- Delegate actions between accountsThis allows one address to explicitly act on behalf of another.
- add reputationunifying history and credentials distributed across different addresses.
- Connect identities across your networkwhich allows for associations between accounts residing on different blockchains.
Possibility of use in real life
In fact, users can split their activities across multiple wallets.
One for storage, one for interacting with applications, one for signing messages, one for payments, and one focused on privacy. Although this separation is common, applications have no standard way to recognize it.
ERC-8092 allows users to declare which accounts are associated. When an application detects that link, it can recognize the actions performed from another address. without asking for additional steps.
As explained, this process takes place without transferring funds or disclosing balances, and you may cancel the relationship at any time.
Possible disadvantages of using a “multi-chain account”
These types of partnerships can also pose challenges.
The possibility of linking multiple addresses with the same ID increases the risk of correlation between accounts that currently remain separate, which can have privacy implications if: Applications and third parties access that information indiscriminately.
Additionally, poor permissions and delegation controls can amplify the impact. OPERATIONAL ERROR OR SECURITY BREACHby extending its effect to multiple related accounts.
However, the ERC-8092 design includes mechanisms to mitigate these risks.
For example, you can save associations. in chains you Off-chain. On-chain storage prioritizes transparency and configurability, while off-chain storage aims to reduce costs and increase scalability. Users restrict the publication of links between their accounts.
Additionally, associated accounts can be disassociated at any time.
Standards define the rules Verify the date, verify the signature, check if the link is still validThis reduces the impact of old associations, configuration errors, or delegations that you don’t want to keep active.
How will 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 account authorizes it, when it’s valid, and optionally in what context it’s used.
The second is the Signed Association Record (SAR). this Wraps the AAR with the associated account’s cryptographic signaturetype of key used, and link revocation status.
Both accounts sign the same structured messages using EIP-712, the Ethereum standard that defines how to sign data in a readable and verifiable manner. The result is Cryptographic certification without intermediarieswhich can be verified in any application.
According to that document, ERC-8092 supports multiple transaction signature schemes.
- Ed25519 (Common in networks such as Solana).
- BLS12-381 along with the method that enables the use of passkey And biometric authentication.
- Smart contract signing via ERC-1271 and ERC-6492 is also being considered.
ERC-8092 aims to provide a common technical framework for declaring, validating, and managing associations between accounts, with the aim of facilitating the development of multi-chain identities.