**wallets need to natively support more web3 identity elements.**

crypto is about much more than just your tokens and NFTs. concretely this means:

Catholic, husband, father; building Ethereum Follow Protocol; ENS (DAO delegate, former core team); Sign-in w/ Ethereum (creator)

- free ENS subdomains
give new users a free off-chain ENS subdomain (via ccip-read) and a free starter ENS profile avatar as part of the wallet creation process. Coinbase Wallet is an example of a wallet that offers free off-chain ENS subdomains to its users...

...creating a wallet without an ENS name and profile should only be something advanced users do for a specific purpose, not the default for the average user being onboarded to web3

- wallet as profile
redesign the wallet UI as a profile, displaying the user’s ENS Primary Name as their username, their ENS profile’s avatar as their avatar, other profile data from their ENS records, roles they have in major DAOs, their 
EFP followers and followings, etc in addition to their assets...

...The tokens and NFTs they own are simply part of this greater web3 profile. Rainbow Wallet is an example of a wallet pioneering this approach

- SIWE support
recognize a sign-in with ethereum message signing request and display it with a unique UI that makes it clear what it is compared to other message signing requests. M*taM*sk is an example of a wallet that already does this.