baycurrent.eth - baycurrent.eth ENS Profile

View baycurrent.eth's Ethereum and EVM-compatible blockchain wallet address: 0x4f29ae8480537a1c20b7e17e995edc9337f5dddb. Track real-time onchain transactions, token holdings, NFT collections, and DeFi activities associated with this Web3 identity.

baycurrent.eth is the decentralized Web3 identity and digital profile of 0x4f29ae8480537a1c20b7e17e995edc9337f5dddb active since Sep 27, 2022. This comprehensive Web3.bio profile page showcases baycurrent.eth's complete Ethereum Name Service (ENS and .eth domain) presence, onchain activities, and reputation across the ENS ecosystem and broader decentralized web. This Web3 profile aggregates baycurrent.eth's complete onchain activity history for wallet 0x4f29ae8480537a1c20b7e17e995edc9337f5dddb, 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 baycurrent.eth's contributions, reputation, and engagement across the decentralized ecosystem. Explore baycurrent.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 baycurrent.eth's journey and contributions across blockchain networks and Web3 communities.

Connect with baycurrent.eth across 3 connected social accounts (2 verified): sakana_eth on Twitter (X), 0xsakana on Farcaster (verified), asumin.lens on Lens (verified). These verified social connections link baycurrent.eth's Web2 and Web3 digital identities across multiple platforms.

Alternative ENS pages: baycurrent.eth.limo, baycurrent.eth.xyz, baycurrent.eth.page, baycurrent.eth.id, baycurrent.eth.sucks, baycurrent.eth.box, baycurrent.eth.cd and ens.app/baycurrent.eth, efp.app/baycurrent.eth, vision.io/baycurrent.eth