Web3 Labs 🌐3️⃣🥼

❓Are you developing DApps, smart contracts, or wallets using android and have used by any chance Hyperledger #Web3j? If so, or only if you thought about it, we want to hear from you! 👇

Enscribe is turning ENS into a team product. At @EthCC, they demoed: • multisig support • shared access • batched operations • API + CLI for automation This is infra for serious protocols. buff.ly/9HaolDU

The latest project to embrace ENS for naming their smart contracts is @ssv_network! @ENS_DAO Contract Naming Season continues to gather momentum. 🔥

.@ssv_network, Ethereum’s leading DVT infrastructure, has adopted ENS-based naming for its smart contracts as part of @ens_dao Contract Naming Season. With 7.5M+ ETH secured and ~19% of validators running on SSV, contract identity matters at this scale. 👇

Enscribe’s beta (shown at @EthCC) is all about teams. You can: • create an org • invite members • manage namespaces together • track changes + activity Onchain identity is no longer solo — it’s collaborative. buff.ly/9HaolDU

Imagine trying to understand a protocol where everything is labelled with random strings. That is still how most onchain systems operate today.

The most common reason organisations don't adopt ENS isn't technical. It's that they don't want to manage another identity and don't want to lose the legal protections their existing domain provides. DNSSEC import solves both.

Enscribe at @EthCC wasn’t just a demo… It was a pivot. From simple ENS naming → to a full org-level identity layer for web3 teams. Think: • shared workspaces • contract management • structured namespaces buff.ly/MCFgfjG

At @EthCC, Enscribe showed its next evolution: 👉 from naming contracts → to powering full team onchain identity The new beta lets orgs manage: • namespaces • contracts • metadata All in one place. This is a big shift buff.ly/9HaolDU

Earlier this week we announced a big change with @enscribe_. From our work in contract naming season, with leading teams including @Corkprotocol, @LiquityProtocol, @nounsdoteth and @Giveth, we realised there's a shortage of org-first infra for ENS. Enscribe is now fixing this.

Most teams track their contracts in docs, spreadsheets, and internal notes.
 Users never see that structure. Enscribe brings that structure onchain, so every contract your team deploys is clearly named, organised, and recognisable.

Enscribe tutorials are designed to be quick and practical Most are under three minutes and focus on one clear task so you can learn and apply immediately.

Working with teams like Nouns DAO, Liquity, Cork and Giveth showed us something important Naming contracts is easy Understanding everything you have deployed is not

Yesterday we shared a huge update for @enscribe_ at @EthCC. If you want to see the announcement in full, check out @nischalsh11's talk. youtube.com/live/-L5zE16FF…. Big props to the EthCC team for having a livestream where we could share straight after the talk.

ENS is for humans, organizations and agents. Nischal repping ENS hard at @EthCC. Some ENS ninjas found in the room too. 🥷🥷🥷

An important clarification for anyone working with ENS. Forward resolving names and primary names are not the same thing. That distinction defines a real security boundary.

Most ENS usage today is personal But the real opportunity is organisations Protocols, DAOs, teams and apps all have infrastructure that should be human readable

Set those reminders, just over 2 hours until the biggest update @enscribe_ has made since launch at @EthCC! If you're a team or org building on Ethereum who cares about identity using ENS or DNS you don't want to miss this.

The Enscribe community calls are now live on YouTube This is where we go deeper into the why behind contract identity and show what we are building in real time.

If you’re at @EthCC and a project who wants to do more with @ensdomains, make sure you make it along to @nischalsh11’s talk. Huge new update being announced for @enscribe_, you won’t want to miss this. Onchain identity is about to get a lot simpler for teams.