2026
- January 14 - Liquity x Enscribe: Liquity introduces ENS-based naming for core protocol contracts
- January 16 - The Enscribe homepage now features card-based navigation and a new search modal
- January 23 - How to perform onchain versioning of smart contracts
- January 27 - Cork adopts ENS-based contract naming with Enscribe
- January 29 - ENS Contract Naming Season update 1
- February 3 - Giveth introduces ENS-based naming for core smart contracts with Enscribe
- February 4 - Why smart contract names are not discoverable by default
- February 5 - Get ready for the first Enscribe Community Call
- February 11 - Based Nouns introduces ENS-based naming for its smart contracts with Enscribe
- February 12 - Why primary vs forward-resolving names is a security boundary
- February 19 - How to manage versions in upgradeable smart contracts
- February 20 - Why smart contract audits don't prevent contract impersonation
- February 25 - Blockscout introduces contract identity scoring via Enscribe
- February 26 - Common smart contract naming mistakes
- March 4 - Why identity is a shared responsibility, not a feature
- March 5 - Enscribe Community Call #2: UI revamp, API docs, and contract metadata
- March 6 - Name Explorer: Navigate ENS hierarchies and metadata
- March 10 - Contract Metadata: Rich onchain identity for smart contracts
- March 11 - Ask AI to query ENS and name your smart contracts
- March 12 - ENS Contract Naming Season awards: first distributions and what comes next
- March 18 - Why hexadecimal addresses are still a security problem
- March 19 - Enscribe API documentation
- March 24 - Enscribe launches its YouTube channel
- March 26 - DNS on ENS and why optionality matters
- March 31 - From contract naming to identity infrastructure
- April 9 - What DNS taught us about organisational naming, and why ENS is following the same path
- April 15 - Enscribe at EthCC [9]
- April 16 - Why your DNS domain is the easiest way into ENS
- April 21 - SSV Network joins Contract Naming Season
- April 23 - How to design an onchain namespace — lessons from 30 years of DNS
- April 29 - Name History for ENS names
- April 30 - Why ENS adoption looks like DNS adoption did in 1995
- May 11 - Superfluid joins Contract Naming Season
- May 25 - Kleros joins Contract Naming Season
- May 29 - Reflections on ENS Contract Naming Season
- June 10 - Sign in with Ethereum and self-managed naming
2025
- March 21 - Simplified Smart Contract Naming With Enscribe
- March 26 - Enscribe Now Supports Linea Sepolia Testnet
- April 3 - Enscribe Now Supports Base Sepolia Testnet
- April 10 - Easily Encode Solidity Constructor Arguments With Enscribe
- April 18 - The New Enscribe Docs Are Live
- April 23 - ReverseClaimable and ReverseSetter Support for Naming Contracts with Enscribe
- April 25 - Enscribe Now Live on Ethereum, Linea, and Base Mainnets
- May 1 - How To Easily Name Your Existing Smart Contracts
- May 12 - Integration of Contracts Verification in Enscribe
- May 15 - Beyond Naming Smart Contracts
- May 22 - Be like Heroku – Introducing Auto-Generated ENS Names for Your Smart Contracts in Enscribe
- June 4 - Easily Find Your ENS Names for Naming Smart Contracts
- June 10 - Explore Accounts, Contracts and ENS Names Across Multiple Chains
- June 20 - Quickly Find Your ENS Names in the My Account View
- June 26 - Share the Love and Claim an Exclusive POAP as an Early User of Enscribe!
- July 4 - Ethereum Follow Protocol (EFP) Support in Enscribe
- July 10 - ENS Reverse Registrar Support in Alloy for Rust Developers
- July 18 - Increasing Trust in Smart Contracts with the Contract Deployer Address in Enscribe
- July 24 - Explore Contract Labels with the Open Labels Initiative in Enscribe
- July 31 - Enscribe UI Now Supports Dark Mode
- August 8 - Safe Wallet Support in Enscribe
- August 13 - Enscribe Now Supports ENS L2 Primary Names
- August 29 - Enhancing the Contract Details Experience on Enscribe
- September 3 - ENS Names Come to Enscribe URLs!
- September 12 - ENSIP: Contract Metadata Standard and Text Records
- September 18 - Understanding ENS & Contract Naming Trends: Insights from Our Dune Dashboard
- September 25 - Simplifying Naming
- October 1 - Introducing the Guides Section
- October 7 - Low-Risk DeFi Needs Human-Readable Smart Contracts
- October 17 - Smart Contract Naming With Hardhat
- October 23 - Name Your Contracts with the Enscribe Library
- October 31 - Viewing Calldata to Simplify DAO Smart Contract Naming
- November 6 - ENS Contract Naming Season
- November 12 - EnscribeV2 is now live on Ethereum mainnet
- November 28 - Naming your contracts with Basenames
- December 5 - Enscribe Now Available as a Safe App
- December 9 - Announcing the Enscribe Contract Naming Audit Service
- December 11 - Nouns DAO x Enscribe: Bringing Clear, Human-Readable Names to the Nouns Contract Universe
- December 18 - Naming Smart Contracts with Foundry
- December 30 - Batch Naming - Name Multiple Contracts in One Go