Enscribe launches its YouTube channel

Enscribe now has a YouTube channel with short tutorials, walkthroughs, and community call recordings that show how smart contract naming works in practice.
You can find it here: https://www.youtube.com/@enscribexyz
Community calls
The community call recordings are where the more substantial updates live. We have published two so far, and they cover considerably more ground than the tutorials (see below).
The first call introduces the core problem Enscribe is solving, walks through live demos of the web app, and covers the developer tooling, including the Hardhat plugin and Foundry library. It also outlines the roadmap: multisig integrations, Blockscout support, an API release, versioning standards, and contract metadata via ENSIP-25.
The second call, published last week, covers new features added since the first, including an experimental Ask AI feature, a new Docusaurus-powered API docs setup, and contract metadata browsing. The Lighthouse team also joined to discuss how they have implemented metadata for ENS domains, which is a good illustration of how the broader ecosystem is starting to build around contract identity.
If you want to follow what we are building and why, the community calls are the most direct way to do that.
Tutorial videos
The tutorial playlist covers practical developer workflows step by step, including:
- Naming smart contracts on Ethereum mainnet, Linea, and Base
- Managing and naming existing contracts through the Enscribe app
- Using Safe wallet to assign contract names
- Claiming an Enscribe POAP by naming a contract
- Viewing all ENS names associated with an account
Each video is short. Most run under three minutes and focus on a single workflow.
Why contract naming matters
Smart contracts on Ethereum are identified by hexadecimal addresses — identifiers that work well for machines but are difficult for humans to recognise or verify. Enscribe lets developers assign ENS names to contracts, so instead of a 42-character string, users see a readable identifier that reflects what the contract actually is and who published it. The principle is similar to how domain names replaced IP addresses for websites, though the security implications onchain are more significant given what users are being asked to approve.
Subscribe
The channel will continue to grow with new tutorials, developer examples, and community call recordings. Subscribe at https://www.youtube.com/@enscribexyz.
Happy viewing! 🚀