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 Ask AI is not just about answering questions. It is about turning those questions into actions. Ask how ENS works. Or ask it to name your contracts. The same interface supports both.

Ethereum users are still being asked to verify 42-character hexadecimal strings before approving transactions. Address poisoning attacks exist because of this. This needs to stop. We need to build for users, not devs. enscribe.xyz/blog/why-hexad…

Security in DeFi has to be designed, not patched on later. In this clip, @ConorSvensson breaks down how @Corkprotocol is rethinking security from first principles. Worth a watch if you care about safer onchain systems 👇

POV: It’s 2027. You interact with safe.eth, not 0x438ac…. You trust every transaction. Ethereum feels… human. That future starts now.

We believe that anything you can do with a UI, you should be able to do with an agent. To facilitate this, we've added Ask AI to our app! Ask it about an ENS record, or use it to name your contracts and wallets. Shoutout to @namespace_eth for their lookup ens-mcp infra.

Update #3 for today. Enscribe now has its very own ENS agent. Talk to it about ENS or get it to name your wallets and contracts. Agentic ENS is here!!!

Enscribe just introduced Name Explorer, a new way to understand how ENS names are structured. Instead of thinking about ENS purely as resolution, Name Explorer lets you see the full identity structure behind a name.

Enscribe Community Call #2 will also introduce a brand new capability. 🗓 Wednesday March 11 ⏰ 3 PM GMT 📍 Google Meet You can now attach metadata directly to contract identities including GitHub repos, docs, and project context. Identity just became far more expressive.

🚨 Enscribe Community Call #2 is happening! 🗓 Wednesday March 11 ⏰ 3 PM GMT 📍 Google Meet We are walking through major Enscribe updates including a revamped UI, new API docs, contract metadata, and our early Versioning Registrar work. If you care about smart contract identity you should be in this room.

As part of @ens_dao naming season, Enscribe is powering a new feature on @Blockscout! Contract pages now include an identity score, based on @ensdomains configuration. Contract identity now sits alongside verification and risk signals inside the explorer interface. 👇

Here's one you won't want to miss: Abhijeet Bhagat () is tackling Ethereum's biggest UX headaches with "Fixing Ethereum UX and Security: Naming and Trusting Smart Contracts with Enscribe" at the Built on Ethereum track. When users can actually understand and trust what they're interacting with, that's when crypto goes mainstream.

Smart contract addresses are cryptic and users can't tell if they're interacting with legitimate protocols or scams, but Nischal Sharma (@nischalsh11) is tackling this UX nightmare with Enscribe at the Built on Ethereum track. When users can actually read and trust what they're signing, Ethereum becomes accessible to everyone, not just crypto veterans.

The best contracts don’t hide behind hex.

Every day, users still interact with unnamed smart contracts across wallets, explorers, and governance tools. That is confusing, risky, and completely avoidable. Contract Naming Season exists to change that. ➡️

So @Giveth has introduced ENS-based naming for its core smart contracts. Each contract now has a human-readable, verifiable identity, making onchain interactions clearer for donors, builders, and the wider community. Enabled by @enscribe_, @ensdomains and @ens_dao. ⬇️

Contract Naming Season is well underway and the momentum is real. What started as a simple idea is now turning into a visible shift in how teams treat smart contract identity. More contracts are getting names and more users are seeing clarity instead of hex. ➡️

It feels like yesterday we announced Contract Naming Season with the support of @ENS_DAO. We're now almost halfway through. So far, we’ve announced contract naming by @nounsdao, @Corkprotocol, and @LiquityProtocol, with several more protocols currently in progress. 👇

Cork is introducing ENS-powered naming across all protocol contracts, enabled by @enscribe_. Every component now has a human-readable, verifiable identity, bringing greater clarity and safety to onchain interactions.

As part of @ens_dao Contract Naming Season, @corkprotocol has adopted ENS-based naming across its smart contract infrastructure using Enscribe. Its core contracts and wallets now have human-readable, verifiable identities.