Feb 24
Loading video player...
Welcome to the first Enscribe Smart Contract Identity Community Call. In this session, we introduce the core problem Enscribe is solving: Millions of dollars are lost each year due to address spoofing and poisoning attacks, largely because users are asked to trust unreadable hex contract addresses. We walk through: - Why hex addresses create UX and security risks - What “primary contract naming” means (forward + reverse resolution) - How onchain smart contract identity goes beyond simple naming - Hierarchical ENS structures for protocols (org → apps → contracts → versions) - Live demos of the Enscribe Web App - Using the Hardhat plugin and Foundry library to name contracts at deploy time - Batch naming for protocols - Contract Naming Season (in collaboration with ENS DAO) - Our roadmap: multisig integrations, Blockscout support, API release, versioning standards, and contract metadata (ENSIP-25) Enscribe provides open-source infrastructure for naming, verifying, and managing smart contracts and wallets using ENS — replacing hex addresses with verifiable, human-readable identities. Identity for protocols. Privacy for people. 🔗 Try Enscribe: https://app.enscribe.xyz 📚 Learn more: https://www.enscribe.xyz 💬 Join the community: https://t.me/enscribers / https://discord.gg/8QUMMdS5GY