whoshouldwe.base.eth - whoshouldwe.base.eth Basenames Profile
View whoshouldwe.base.eth's Ethereum and EVM-compatible blockchain wallet address: 0xe83ac7040e9722009a58bc73b779aaee20109c32. Track real-time onchain transactions, token holdings, NFT collections, and DeFi activities associated with this Web3 identity.
About whoshouldwe.base.eth
whoshouldwe.base.eth Profile Summary
whoshouldwe.base.eth is the decentralized Web3 identity and digital profile of 0xe83ac7040e9722009a58bc73b779aaee20109c32 active since Sep 16, 2025. This comprehensive Web3.bio profile page showcases whoshouldwe.base.eth's complete Basenames (.base.eth domains) based on ENS presence, onchain activities, and reputation across the Basenames ecosystem and broader decentralized web. This Web3 profile aggregates whoshouldwe.base.eth's complete onchain activity history for wallet 0xe83ac7040e9722009a58bc73b779aaee20109c32, featuring NFT collections, POAP event attendance records, Paragraph / Mirror / Contenthash IPFS articles, DAO governance participation in Snapshot and Tally, Guild memberships, Talent/Human Passport/Ethos scores, and Farcaster/Lens/Polymarket social feeds. Discover whoshouldwe.base.eth's contributions, reputation, and engagement across the decentralized ecosystem. Explore whoshouldwe.base.eth's comprehensive Web3 identity hub to discover their digital footprint, social graph, onchain reputation scores, NFT portfolio, DAO memberships, and decentralized social activity. This profile provides a transparent, verifiable view of whoshouldwe.base.eth's journey and contributions across blockchain networks and Web3 communities.
whoshouldwe.base.eth Contact and Social Accounts
Connect with whoshouldwe.base.eth across 2 connected social accounts (1 verified): aas6 on Farcaster (verified), ramacha33884859 on Twitter (X). These verified social connections link whoshouldwe.base.eth's Web2 and Web3 digital identities across multiple platforms.
๐ฅ AI Roast