.png){kind=logo}
Ethereum developers have drafted ERC-8092, a proposed standard that sets rules for “associated accounts” on Ethereum and other chains. The draft describes how two accounts can attest to a relationship with signed data and later end that relationship when circumstances change.
Wallet sprawl has become common across crypto. Many users separate wallets by purpose, risk, or platform, while organizations split wallets by permissions and operational roles. This fragmentation complicates daily tasks, such as delegation and ownership proofs. Many teams rely on app-specific solutions.
ERC-8092 proposes a common method for expressing relationships between blockchain accounts while leaving control with the owners of those accounts. The draft supports linking addresses when a user or application needs proof of association. It does not require users to collapse activity into a single, permanent public identity. Developers highlight several intended uses, including sub-account structures, delegated permissions, and combining reputation across wallets.
In addition, the proposal responds to practical limits in current wallet management. Several users coordinate across addresses through off-chain logins, shared credentials, or manual verification steps. These workarounds can reveal more information than necessary and often create inconsistent records. For organizations, they can also make audits harder, especially when teams must keep a clear separation between roles and permissions.
The specification defines two records that applications can verify. An associated account record captures the initiator, approver, validity timestamps, and optional context. A signed association record adds both signatures and a revocation status. Third parties can verify the relationship without a trusted coordinator.
ERC-8092 uses EIP-712 typed data signing so wallets can present structured messages to signers. The draft also supports several signature schemes, which can help different wallet types participate. It includes smart contract signatures through standards such as ERC-1271, alongside options like passkeys and other cryptography used outside the EVM.
Furthermore, developers designed the proposal to support different privacy and cost preferences. Teams can store associations on-chain for composability or store them off-chain for scale. Either party can revoke an association at any time, and the draft includes validation rules for timestamps, signature checks, and revocation state.
ERC-8092 aims to work beyond the Ethereum mainnet because users and applications operate across Layer 2 networks and other chains. Developers expect dApps to use the standard for cross-chain permissions. The proposal uses ERC-7930, which sets a standard address format that includes chain context. This format lets applications express and verify account relationships, even when the linked accounts sit on different networks.
The draft is still under community review, so it will need implementers before it reaches everyday users. Wallet providers, DAOs, and identity platforms would need to support the record formats and verification logic. Developers have already opened discussion channels and shared early reference work to help others test and evaluate the standard.
Also Read: Ethereum News Today: ETH Eyes $4,955 as Inverse Pattern Meets Whale Support
