3NS

3NS (Web3 Naming System) is an AI-first domain naming protocol that transforms .Web3 domains from passive identifiers into autonomous agents. Rather than simply resolving a wallet address or hosting a profile page, a .Web3 domain registered through 3NS carries embedded AI logic, workflow definitions, and on-chain governance — enabling it to negotiate transactions, route payments, and execute automated tasks on behalf of its owner.

The Problem It Solves

Existing blockchain naming systems — including .sol on Solana, .eth on Ethereum, and similar services — resolve human-readable names to wallet addresses. They serve a lookup function. 3NS argues this is insufficient for an agentic web where software agents need to discover, trust, and transact with each other autonomously. A .Web3 domain on 3NS is designed to serve as a persistent, discoverable identity for an AI agent: something that can be queried, authenticated, and instructed to act without human intervention at each step.

Core Mechanism: The Agent Domain Protocol

The foundation of 3NS is the Agent Domain Protocol (ADP), an open-source standard published under the MIT license at github.com/3nsai. ADP defines a structured way to attach AI-driven intelligence to a blockchain domain and make that intelligence discoverable and interoperable across networks.

Each .Web3 domain stores a protocol_spec.json file containing its AI logic, workflow definitions, and chain-specific registry metadata. This specification describes what the domain-as-agent can do, what frameworks it uses, and how other agents can interact with it.

The protocol is built around three layers:

Domain architecture — Domains are tokenized, multichain entities registered across supported blockchain networks. Each domain includes a decentralized identity (DID) record, registry and resolver contract addresses per chain, and metadata anchoring it to a subgraph for indexing.

Discovery and reputation — ADP includes a metadata indexing layer that allows agents to find each other autonomously. Domains accumulate reputation scores based on performance metrics and verifiable credentials, giving other agents a trust signal before initiating interactions.

Workflow engine — Domain-agents execute tasks using a workflow system compatible with N8N and ActivePieces, two popular visual automation tools. Operators can configure drag-and-drop workflows without writing code, while developers can build more complex automations using node architecture from the protocol. Workflow nodes handle operations including payment processing with escrow, oracle data fetching, off-chain API calls (Google Places, Sheets, Firebase), and on-chain function calls.

Key Products and Features

The 3NS platform ships as a set of interconnected components. The web3names-app is a browser-based dApp for registering and managing .Web3 domains, configuring agent workflows, and publishing Linktree-style landing pages tied to a domain on-chain identity. The web3names-snap is a MetaMask Snap plugin enabling direct wallet-based domain interaction. 3NS Smart Contracts are a fork of the Ethereum Name Service (ENS) registry and resolver contracts, modified to support ADP functionality including agent logic storage and tokenized governance. The 3ns-subgraph is a subgraph indexing layer for optimizing domain discovery across supported chains. The Agent Domain Protocol node package is an open-source TypeScript implementation of the ADP core, providing developers the tools to build and connect agent-enabled domains.

The platform also allows users to build AI agents with memory and tool-calling capabilities, and to export domain configurations to GitHub or directly to a blockchain.

Blockchain Support and Solana Integration

3NS is designed as a multichain protocol. Its smart contract infrastructure currently supports Ethereum, Moonbeam, Polygon, Base, Near, Solana, and Stacks (for Bitcoin ordinals). The ENS-derived registry and resolver contracts are deployed across EVM-compatible chains, with Solana listed as a compatible deployment target — meaning .Web3 domain NFTs can be issued on Solana in addition to EVM chains.

The project GitHub documentation identifies Solana as a collaborative partner alongside Near and Polkadot. The protocol is EVM-first in its current implementation — the modified ENS contracts run natively on Ethereum and Moonbeam — with Solana participation through cross-chain interoperability rather than a native Solana smart contract deployment.

AI Framework Compatibility

ADP is deliberately framework-agnostic. The protocol supports agent implementations built with LangChain, Google GenKit, Autogen, CrewAI, and Fetch.ai, allowing developers to bring existing agent code and expose it through a .Web3 domain identity. The system also integrates with Ollama and OpenWebUI for self-hosted model deployments, supporting operator data-privacy preferences.

Governance

.Web3 domains can be tokenized into collectives — on-chain DAOs where native token holders direct domain-agent behavior and share in any revenue generated. Governance occurs transparently through voting contracts, with on-chain versioning and rollback capabilities for domain configurations.

Security and Audit Status

No independent security audit of the 3NS smart contracts or the Agent Domain Protocol has been publicly documented. The protocol notes that private repositories exist for components under active development — including an autonomous WebRTC agent-to-agent communication protocol and the Collective DAO framework — and that these are being refined based on community input before public release. Prospective users should treat the protocol as early-stage and conduct an independent assessment before deploying production workloads.

Team and Background

3NS operates under the GitHub organization 3nsai with public repositories licensed under MIT. No individual team members are publicly identified in project documentation. The project maintains a Discord community and social accounts at @3nsdomains on X. Early user reviews from September 2025 highlight multi-LLM switching, agent workflow automation (including integrations with n8n for accounting and wallet management), and data-privacy controls as valued features, with pricing cited as the primary concern for individual users.

Ecosystem Fit

3NS enters a competitive segment alongside Solana Name Service (.sol domains), Unstoppable Domains, and ENS — but targets a distinct use case. Rather than replacing human-readable name resolution, it aims to become the identity and discovery layer for autonomous AI agents operating on-chain. As agent-to-agent communication becomes a larger part of Web3 infrastructure, a standardized protocol for publishing, discovering, and trusting agent identities occupies a meaningful position. Whether 3NS or a competing standard captures that role remains open, but the Agent Domain Protocol open-source, framework-agnostic design represents a reasonable early attempt to define what machine-readable blockchain identity looks like for the agentic era.