Web3.bio

Decentralised Social isn’t just “social on-chain.” It’s owning your identity. Carrying your reputation anywhere. Joining communities that aren’t locked in walled gardens. When your social graph lives on public infra, platforms compete for you, not the other way around. That’s the shift 🔓✨

@masknetwork @xmtp_ @LC @orb_club @thefireflyapp 🙌

Onchain social just went full degen mode 😈🔥 @xmtp_ x @masknetwork x @LC x @orb_club x @thefireflyapp = 🔒 Encrypted by default 🌐 Cross-app, cross-ecosystem messaging 🤖 Humans + AI agents in one programmable layer Message anywhere. Reach anyone. Decentralised social graph just leveled up 🚀

@btcbabycow @garyintern @masknetwork Firefly 是客户端， Web3.bio 更多是个人页面，适合分享 😊

@garyintern @masknetwork @web3bio 这个和firefly 一样？

@yanbo2004 @garyintern @masknetwork 🫡

@garyintern @masknetwork @web3bio 我买ens就为了这个

@0xhardman @garyintern @masknetwork 欢迎提建议，每周迭代🔁。

@garyintern @masknetwork @web3bio 这个项目真的是宝藏，聚合了地址相关的社交身份，作为一个区块链从业者，应该在上面拥有一个自己的名片。 web3.bio/0xhardman.eth

谢谢🙏 Web3.bio profile 页面聚合了主流 Web3 身份（ @ensdomains @LC @farcaster_xyz Basenames 等）、社交链接、成就分数、动态、参与活动和组织等，可作为 Web3 Linktree 链接或者身份浏览器。

Identity layer and bridge between Web2 and Web3 🙌

@miyaspokeofthis @efp Hi again, your MetaMask.eth seems to be redirecting to metamask.eth. Some other apps still don’t handle this well. Do you know what the best practice is?

I know that my unusual primary ENS prevents things like refreshing my @efp (which defaults to krys.eth) - so the socials there can't be refreshed either unless I temporarily change my primary resolver 😅 Not sure if it's also causing this issue here. On EFP the wallet address pings between krys.eth (previous primary ENS) and metamask.eth - but then the name collision makes it revert back to krys.eth But krys.eth cannot be refreshed as it would just refresh to metamask.eth without updating the records 😅 That primary ENS is usually the cause of weird wallet issues 😅

We’ll continue showing your ENS names, records, and related social stuffs right on your Web3 profile pages. ➡️web3.bio/vitalik.eth Developers can also grab ENS names and records through api.web3.bio if apps need to resolve ENS ↔️ Address, including records and more.

@miyaspokeofthis @efp Yes, I think this is the root issue. We changed the logic and are refreshing all data (others may have same issues) right now and your records are good now, the connection to your other identities will be fine once the process is finished.

@forlbb 是的，我们这有一些东西也因为不用考虑 Namechain ，简化了。

过去的一年，我一直关注 ENSv2 的进度，伴随着以太坊的扩容，不可避免地能够感受到，一个单独 L2 的必要性在持续地走向消失 🫠 我不喜欢一个项目不断地引入复杂性，所以，这个消息让我这种强迫症感觉非常舒爽 😊

@miyaspokeofthis We can see your record changes in the database, but something prevented the update from completing on our side. We’re investigating the issues. 🙏

Just noticed where the data is being pulled from. Looks like it's pulling ENS data on names that have the ENS record, but in the case of krys.eth it's not accurate as the records changed ~2 weeks ago. In other cases, when there is no ENS record, it pulls data from farcaster and basenames. As for example on hardcoded.eth Not sure how frequently it updates those records or how it's being handled when the records between basename and farcaster differ 🤔 Imho it should just default to ENS records - the specific domain records OR the primary resolver records (usually the most accurate data source).

Hi, thanks for the long reply. Let me try to explain these questions. We refresh data every four hours, so ENS and Basenames updates can range from 1 s to 4 h. The updates are powered by ENSNode, which indexes RPC data instantly and all requests are further cached via Cloudflare. All social links are consolidated from the identities listed on the left side (ENS, Basenames, Farcaster, Lens, etc.) which is what we called Universal Profiles. Hovering over a link card reveals its source. I noticed that your krys.eth profile is outdated and not linked to other identities. Also the normalized name hasn’t been fully fixed on our end (we applied a patch once). We’ll investigate these issues and follow up later. Thank you again. Meanwhile, we are fetching the first ETH transaction time to generate better creation dates, but there are a huge amount of data to query. We are still working on the profile page customization so you can show or hide specific widgets and links.

Hmm... some of the ENS profiles tied to the same wallet address show farcaster while others do not. None show the correct records for socials changed ~2 weeks ago. Seems like that data is either updated infrequently or not pulled from ENS? Betting on the later since names without social records will also display the old socials. Where is that data being pulled from, since it's not being pulled from ENS records themselves? Wouldn't it make sense to pull that data from the particular ENS records or alternatively from the primary resolver of a wallet (as that one will most likely be most up to date)? krys.eth lacks lookup for ens, basename and farcaster ENS lookup for different profiles is looking up the primary resolver for an address instead of that particular ENS name. In case of not-normalized ENS, the lookup shows case sensitivity but the address that shows is normalized. So it basically points to a different wallet address. Date joined isn't related to a wallets age, it shows the ENS creation date which can differ massively from someone's actual time in web3. Would make more sense to actually show the date joined (wallet) + ENS creation date. Passport score should imho be nuked since their scoring is flawed and they refuse to actually fix it. Some users onchain activity, which used to be maxxed out, got nuked to zero at some point. Which means the only way to get a passable score is doing KYC stamps on your public wallet. Which is a ridiculous requirement. (x.com/miyaspokeofthi…)

@altagers @Drei3180 @baseapp @farcaster_xyz @amphib0ly @neynarxyz @ethos_network yes, they told me already, and I will update soon. 👏

@web3bio @Drei3180 @baseapp @farcaster_xyz @amphib0ly @neynarxyz @ethos_network Yes, I mean that the talent builder score is no longer relevant. x.com/0xmacedo/statu…

If you want to take the growth of your account on @baseapp and @farcaster_xyz seriously, add and use the mini app 🔥Scored: Neynar and all scores by @altagers every day There you can track your current rankings: •Quotient by @amphib0ly •@neynarxyz •@ethos_network •@inflynce Understanding how to work with these scores is one of the most effective ways to grow your account. 💰Plus, the app includes a daily check-in with 7-day reward pools in $DEGEN - monitor the quality of your account and earn money at the same time

@altagers @Drei3180 @baseapp @farcaster_xyz @amphib0ly @neynarxyz @ethos_network Please share your thoughts on what we could add.

@Drei3180 @baseapp @farcaster_xyz @amphib0ly @neynarxyz @ethos_network and even nonce transactions on base and @web3bio universal profiles Huge thanks for sharing & supporting! 🫡

1/5 Decentralised social won’t win by fighting X. It wins by outlasting it. Here’s @suji_yan view on where decentralised social —and @LC headed 🧵👇

With @thefireflyapp's support, you can check out both Polymarket and Opinion feeds on any Web3.bio profile.

Decentralised social has been “about to blow up” for years… yet X, IG, and TikTok still own our attention 😤 In this interview, @VitalikButerin & @suji_yan dissected why it’s not the idea that’s broken. Rather, it's because distribution is brutal, incentives are misaligned, and the stack is still too complex🧵 The next breakout for decentralised social won’t come from hype 🚫 It’ll come from systems-level moves that quietly compound… until switching feels inevitable 🚀

Full announcement: lens.xyz/news/mask-netw…