Logo Caption

AgentStack User Guide

This guide helps you safely mint, configure, and manage your Web3 agent domains using the AgentStack naming layer on the Freename.com platform, accross supported blockchains like BNB, Polygon, Solana, Base, and others. 

Whether you’re naming a smart wallet, AI assistant, or autonomous agent, these best practices will help you:

• Avoid technical issues or duplicate conflicts

• Ensure your domain resolves correctly

• Understand key Web3 naming behaviors (like chain-specific identity)

🧭 Web3 naming isn’t like traditional domains - it depends on blockchain-specific rules. AgentStack follows best practices to help you avoid issues that many platforms don’t explain, so your agents can act with trust, clarity, and security from the start.

What is AgentStack?

AgentStack is a naming layer designed for the next generation of AI agents - built entirely on the Freename.com Web3 domain system.

Our domains provide secure, flexible, and user-owned identity options that work across supported blockchains like BNB, Polygon, Solana, Base, and others. Each domain you mint (e.g., me.agentid or chat.agentwallet) becomes a unique on-chain asset - ideal for agent identity, wallet routing, and automated interactions.

🛠️ All domains operate within the Freename ecosystem and rely on Freename’s resolver for proper DNS resolution. External systems like ENS or UD are not compatible unless explicitly configured.

🔐 AgentStack is modular, decentralized, and chain-agnostic within Freename - offering strong interoperability as long as exact-name logic and DNS rules are followed.

How to Mint Your Agent Domain

Step 1: Choose Your Agent Name

Pick a name that reflects your agent’s purpose - like me.agentid, chat.agentwallet, or support.agentprivacy. 

Each domain you mint becomes a unique, user-owned NFT inside the Freename system.

🧠 Tip: Keep names short, clear, and easy to type. Think of it like choosing a wallet name or smart login - agents use this as their identity anchor.

Step 2: Select a Supported Chain

When minting, you’ll be asked to choose a blockchain: BNB, Polygon, Solana, Base, and others.

Your domain will be minted as an NFT on that chain, and it will be resolved using Freename’s DNS tools.
You can read more about minting on Freename here.

🧠 Tip: If you plan to mint multiple domains under different TLDs, try to use the same chain for all of them. This keeps your agent ecosystem unified and avoids the need to switch chains or wallets later.

⚠️ Warning: Freename currently allows each of your domains to be minted only once - on one blockchain. If that policy ever changes, we strongly recommend against attempting to mint the same domain name (e.g., me.agentid) on multiple chains - even it technically possible in the future. This protects trust and ensures reliable resolution across the Freename system

💡 Note: In advanced cases, some users may choose to mint AgentStack domains across different chains and coordinate them using bridging logic. This requires careful setup and is not covered in this guide. For more, see our AgentBridge page.

Step 3: Confirm and Save

Once minted, your domain is yours - no renewals needed. It will appear in your Freename dashboard and in your wallet (as an NFT).

📥 Save the domain, wallet address, and chain information securely.

🔐 Optional: Consider trademark protection if your name is business-critical or publicly promoted. While Web3 offers strong ownership, legal protection adds another layer of defense.

How to Configure Your Agent for Name Resolution

Step 1: Enforce Exact Name Matching

Agents should be configured to accept only full domain names that exactly match what you’ve minted - such as:

me.agentid  

wallet.agentprivacy  

support.agentchat

Avoid partial names like "me" or "agentid" - they may lead to ambiguous resolution.

🧠 Tip: Add a validation rule in your agent’s logic to check the exact string (e.g., me.agentid), not just the user’s input. Reject anything that does not match your domain list.

Step 2: Use Freename’s All-DNS Resolver

To ensure proper mapping of domains to wallet addresses, your agent or dApp must resolve domains through Freename’s all-DNS resolver.

⚠️ Do not rely on default wallet settings (e.g., MetaMask, Trust Wallet) unless configured to prioritize Freename.

🧩 Recommended:

• Use Freename’s DNS resolver endpoint (details in Freename dashboard).

• Test name resolution with MetaMask using “Custom DNS settings” if supported.

Step 3: Block External TLDs

Your agent should reject names that are part of other ecosystems (e.g. .eth, .crypto, .bit) unless explicitly trusted.

Example: If the name is me.agentid.crypto, it should not be accepted, even if similar to your domain.

🔒 Add a rule: If TLD ≠ (.agentid, .agentwallet, etc.)→ Block or flag as invalid.

📥 Optional: Maintain an Allowlist

For added security, maintain a list of approved domains: ["me.agentid", "support.agentprivacy", "vault.agentwallet"]

Only these can trigger transactions, identity actions, or wallet access.

💡 Reminder: Agents are only as trustworthy as their logic. Configure them to act only on verified, exact-match names resolved through the correct system.

Duplicate Risk & Future Chain Support

You Can’t Mint the Same Name on Multiple Chains (Yet)

Every domain you mint - like me.agentid or chat.agentwallet - must be created only once, on a single blockchain (e.g., Polygon or BNB). Even though Freename supports multiple chains, your SLD can only exist in one location.

⚠️ Duplicate minting is currently blocked by Freename’s system. You can’t create the same name on multiple chains - and that’s a good thing. It keeps trust, identity, and resolution safe

Why This Matters

Choosing the right chain from the beginning helps you avoid:

• ❌ Agent errors or lost functionality

• ❌ Conflicts with metadata or wallet routing

• ❌ Loss of control over your domain’s identity

✅ Mint once, on one chain — and keep it simple.

What if You Need to Switch Chains?

If you made a mistake, or if your agent stack is moving to a different blockchain:

• There’s no automated way to move your domain.

• You may contact Freename Support to inquire about possible options, but assistance is not guaranteed.

• You may need to burn the old domain or request unbinding (if supported).

💡 Tip: Double-check your agent’s architecture and chain preferences before minting.

Changing later is difficult and not guaranteed.

What About Cross-Chain Usage?

Freename Domains Are Currently Chain-Specific

When you mint a domain (e.g., me.agentid), it only exists on the blockchain you chose - like BNB, Polygon, or Solana. There is no automatic sync or resolution across chains.

Future Possibility: Cross-Chain Support

Freename currently supports minting each domain on one blockchain only. Even if that ever changes in the future, we strongly recommend choosing a single chain per domain to maintain clarity, avoid conflicts, and ensure consistent resolution.

Cross-Chain Use Today

If you switch blockchains:

• There’s no bridge yet - domains do not sync or carry over.

• You’d need to mint the name again (⚠️ not recommended)
or contact Freename Support to inquire about options.

• Avoid keeping duplicates - even if that becomes technically possible later.

✅ Best Practice

Choose your preferred chain before minting. For domains that work together (e.g., .agentid, .agentwallet, .agentchat), we recommend minting them on the same chain to ensure consistency.

💡 Why It Matters

Even small mismatches - like minting the same name on two chains - can break trust or disrupt agent workflows.

Many agent systems depend on verified, chain-specific identity.

🧭 This isn’t a limitation of AgentStack - it reflects how most of Web3 works today. Other platforms may not warn you, but they face the same technical risks when domains are duplicated or used across chains.

Best Practices for Domain Owners

Stay Consistent Where Possible

• Mint your related domains (e.g. lila.agentname, lila.agentwallet, lila.agentchat) on the same blockchain whenever possible.

• This keeps configuration simple, avoids duplicates, and reduces chances of resolution issues - especially for beginners.

Advanced Setup for Multi-Chain Agents

For agents that interact across blockchains - such as executing transactions on Solana but storing identity on Polygon - minting separate but coordinated domains may be useful.

Example setup:

• lila.agentwallet on Solana (execution)

• lila.agentname on Polygon (identity + storage)

• lila.agentchat on Base (messaging)

⚠️ This setup is more complex, and requires chain-specific logic. If you’re building cross-chain agents, visit our AgentBridge page for more info.

Keep an Eye on Your Name

Duplicate domains are rare - but in decentralized systems, it’s wise to stay aware.

• Occasionally check if your key names (e.g. lila.agentid) appear elsewhere on unexpected chains or TLDs.

• If something seems off, you can:

  • Reach out to Freename support for clarification
  • Consider options like securing the name yourself, or requesting action if appropriate
  • Explore trademark protection if the name is business-critical

🔍 We’re happy to offer suggestions — but each domain owner decides how to respond.

Resolver Configuration Tips

AgentStack domains support different types of resolution depending on how your agent is built and what it needs to access!

DNS Resolution (via Freename)

You can use DNS records (A, CNAME, TXT, etc.) to link your domain to:

• a website

• a config file hosted on IPFS

• or any public content related to your agent

This is the most universal method - ideal for identity documents, static configs, or agent descriptions

Wallet Resolution (via MetaMask & Beyond)

AgentStack domains can currently resolve to wallet addresses using Freename Snaps in MetaMask. This makes it possible to use names like novabot.agentwallet for payments or transfers within supported wallets. Additional wallet integrations may be supported in the future as Freename expands resolver options.

🧭 To enable this today:

• Use the Freename resolver endpoint

• Test resolution inside MetaMask using the Freename Snap

Config-Based Linking (Optional Use)

You may also use domains like novabot.agentid or youragent.agentname to point to agent configuration files hosted on IPFS. This file might contain details like the agent’s purpose, supported inputs, endpoints, or wallet connections.

AgentStack does not host or interpret this logic - we simply provide the domain routing layer.

This approach is useful for:

• Coordinating multi-chain behavior

• Listing metadata for agent discovery

• Structuring agent identity using decentralized tools

Avoid Resolver Conflicts

Some wallets or apps default to other systems like ENS or UD.

To ensure your AgentStack domains resolve correctly:

• Prioritize Freename’s DNS in your settings

• Use “Custom DNS” or “Freename Snap” options in MetaMask

• Avoid overlapping naming across different systems (e.g., don’t reuse the same name on .crypto)

Platform Scope & Compatibility

AgentStack domains operate entirely within the Freename ecosystem. This includes minting, DNS resolution, and resolver endpoint management.

At this time:

• Domains are not natively supported by ENS, Unstoppable Domains, or other Web3 naming systems

• All identity, wallet, and routing logic must be configured using Freename tools or compatible environments (e.g. MetaMask + Snap)

However, the Freename platform is actively evolving - and may support:

• Bridging to other chains or naming systems

• Custom resolver setups for advanced use cases

While AgentStack is currently scoped to Freename, we design for flexibility wherever possible.

If broader compatibility becomes viable, we’ll adapt accordingly.

Disclaimer & Accuracy Notice

This guide is provided for educational purposes only. It reflects current best practices and known limitations within the Freename ecosystem, as understood at the time of writing.

We do not guarantee compatibility with external naming systems (e.g., ENS, UD), future protocol changes, or third-party wallet/platform integrations unless explicitly stated.

The guide was prepared using public information from Freename.com and other open sources believed to be accurate. However, we cannot ensure the completeness or correctness of all technical details, and some features may evolve.

We strongly encourage all users to:

• Verify current policies with Freename directly

• Conduct their own due diligence before minting or deploying domains

• Consult legal or technical experts where needed

We are happy to assist with general guidance, but nothing in this guide should be considered legal, financial, or technical advice.

📄 For full legal and platform disclaimers, see our homepage notice. 

Need Help?

If you’re unsure how to mint, configure, or resolve your agent domain - or you just want to avoid mistakes - we’re here to help.

This project is focused on building Web3 naming layers for intelligent agents.

We offer:

✅ General guidance on naming strategy

✅ Help interpreting Freename platform tools

✅ Suggestions for resolver setup and config files

✅ Feedback on use case ideas or SLD selection

We do not offer technical support, legal advice, or guaranteed integrations. All use is at your own risk and discretion.

📩 Contact: info@dotai.domains