jfcberlin.eth - jfcberlin.eth ENS Profile

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

jfcberlin.eth is the decentralized Web3 identity and digital profile of 0xd552aea491cc87b7e79e81086dfe50ba33bd4f30 active since Jan 4, 2022. This comprehensive Web3.bio profile page showcases jfcberlin.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 jfcberlin.eth's complete onchain activity history for wallet 0xd552aea491cc87b7e79e81086dfe50ba33bd4f30, 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 jfcberlin.eth's contributions, reputation, and engagement across the decentralized ecosystem. Explore jfcberlin.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 jfcberlin.eth's journey and contributions across blockchain networks and Web3 communities.

Connect with jfcberlin.eth across 2 connected social accounts (2 verified): jfcberlin.lens on Lens (verified), cryptojfc on Twitter (X) (verified). These verified social connections link jfcberlin.eth's Web2 and Web3 digital identities across multiple platforms.

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