Many applications and protocols are asking themselves how to identify a user when they have many different wallets or accounts. This is becoming more important for Web3 applications that are integrating more and more Metaverse protocols into a single application. Maintaining that user object with all the mappings becomes cumbersome and is extremely prone to implementation error. There are a certain set of data features that can be explored for different models of creating an aggregated identity for users in the multi-account, cross-chain (MACC) Metaverse.