Logo Caption

AgentStack User Guide

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

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

• Avoid technical issues or duplicate conflicts

• Improve naming consistency and resolver compatibility

• Understand key Web3 naming concepts, including chain-specific identity and resolver behaviour

🧭 Web3 naming differs from traditional domains and may depend on blockchain-specific rules, wallet support, resolver settings, and third-party integrations. This guide provides general best practices to help you navigate the AgentStack ecosystem more safely and clearly.

What is AgentStack?

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

Our domains provide secure, flexible, and user-owned identity options designed for use across supported blockchains such as BNB, Polygon, Solana, Base, and others. Each domain you mint (e.g., me.agentid or chat.agentwallet) becomes a user owned on-chain asset within the Freename ecosystem - ideal for agent identity, wallet routing, and automated interactions.

🛠️ All domains currently operate within the Freename ecosystem and may require Freename-compatible resolver support for proper DNS resolution. Compatibility with external systems such as ENS or UD depends on resolver support and third-party configuration.

🔐 AgentStack is modular, decentralized, and designed for flexible use across supported Freename-compatible environments, while interoperability depends on resolver settings, exact-name logic, and ecosystem support.

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 user-owned on-chain asset within Freename ecosystem.

🧠 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 on that blockchain within the Freename ecosystem, while resolution and compatibility depend on supported resolver tools and integrations. 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 supports minting each domain on a single blockchain within its ecosystem. If multi-chain support evolves in the future, we strongly recommend avoiding the same domain name (e.g., me.agentid) across multiple chains whenever possible. This may help reduce naming conflicts and improve resolution consistency within the Freename ecosystem.

💡 Note: Some advanced users may explore cross-chain naming strategies using third-party tools or custom configurations. These setups vary significantly and are outside the scope of this guide.

Step 3: Confirm and Save

Once minted, your domain is controlled through your wallet within the Freename ecosystem. Most AgentStack domains minted directly through Freename currently do not require recurring renewals. Your domain will appear in your Freename dashboard and associated wallet.

📥 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

When supported by your application logic, agents should preferably use full domain names that exactly match the names 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: Configure Compatible Resolver Support

Depending on your wallet, application, or dApp, compatible resolver support may be required for AgentStack domains to function correctly within the Freename ecosystem.

⚠️ Default wallet or resolver behavior may vary across platforms. Some applications may require additional configuration or Freename-compatible resolver support.

🧩 Recommended:

• Use resolver settings and tools supported within the Freename ecosystem where applicable.

• Test resolution behavior carefully within compatible wallets or applications before relying on production use.

Step 3: Reduce Namespace Confusion

Some applications may choose to restrict or validate supported naming systems to reduce ambiguity or namespace conflicts.

Example: Some systems may choose to reject names that combine multiple naming conventions or unsupported extensions in order to reduce confusion.

🔒 Some applications may optionally validate approved naming patterns or supported extensions before allowing sensitive actions.

📥 Optional: Maintain an Allowlist

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

In some advanced setups, approved domains may be used to limit access to specific actions, identities, or wallet permissions.

💡 Reminder: Agents are only as trustworthy as their logic. Exact-name matching and careful resolver configuration may help reduce ambiguity and improve trust within supported ecosystems.

Duplicate Risk & Future Chain Support

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

Within the current Freename ecosystem, each domain is generally minted once on a single supported blockchain (such as Polygon or BNB). This helps reduce confusion and maintain clearer identity resolution across supported tools.

⚠️ Freename currently restricts duplicate minting of the same domain across supported chains within its ecosystem. This helps reduce identity conflicts and improves consistency for supported resolution tools.

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 Want to Use Different Chain Later?

Cross-chain migration options may evolve over time, but currently users should assume that changing chains after minting can be complex. If needed, you may contact Freename Support to ask about available options within the ecosystem.

💡 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

Within the current Freename ecosystem, domains are generally tied to the blockchain selected during minting (such as BNB, Polygon, or Solana). Automatic cross-chain syncing or unified resolution may vary depending on ecosystem support and integrations.

Future Possibilities for Cross-Chain Usage

Freename currently emphasizes single-chain minting per domain within its ecosystem. If broader cross-chain functionality evolves over time, maintaining a clear primary chain for each domain may still help reduce confusion and improve consistency.

Cross-Chain Use Today

Cross-chain portability features may evolve over time, but users should currently assume that domains function primarily on the blockchain where they were minted. Before changing chains or creating related domains, it’s best to review the latest Freename documentation and ecosystem support.

✅ 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

In some Web3 systems, inconsistent naming across chains may create confusion around identity, routing, or ownership. Keeping related domains organized and consistent can help reduce those risks.

🧭 Cross-chain naming standards across Web3 are still evolving. Different platforms may handle interoperability, resolution, and identity differently over time.

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 Multi-Chain Considerations

Some advanced users may choose to organize related domains across different blockchains depending on their preferred tools, wallets, or ecosystems. This type of setup can become more complex and may require additional configuration and testing.

⚠️ Cross-chain workflows and interoperability standards across Web3 are still evolving. Users exploring advanced configurations should review the latest ecosystem documentation and test carefully before relying on production use cases.

Keep an Eye on Your Name

Because Web3 naming systems can evolve differently across ecosystems, it’s still wise to stay aware of how your names are being used and resolved.

• Periodically review how your domains are configured and represented across the platforms or ecosystems in use.

• If something seems off, you can:

  • Reach out to Freename support for clarification
  • Consider securing related names or variations if they are important to your brand or identity strategy
  • Explore trademark protection if the name is business-critical

🔍 Each domain owner should evaluate their own naming, branding, and security strategy based on their needs and risk tolerance.

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)

Some Freename-supported tools and wallet integrations may allow AgentStack domains to be associated with wallet addresses or identity records. Compatibility and available features can vary depending on the wallet, resolver configuration, and ecosystem support.

🧭 Before relying on wallet resolution features, users should review the latest Freename documentation and test compatibility with their preferred wallets or applications.

Config-Based Linking (Optional Use)

Some users may choose to associate their domains with decentralized storage or configuration systems, depending on available tooling and ecosystem support.

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

Potential use cases may include identity organization, decentralized references, or experimental interoperability workflows.

Compatibility & Resolution Considerations

Different wallets, browsers, and Web3 tools may support naming systems differently.

Users should verify how their preferred applications handle Web3 domain resolution and naming compatibility before relying on production or payment-related use cases.

❗Availability of advanced Web3 records and resolver features may vary across tools, applications, and ecosystem integrations.

Platform Scope & Compatibility

AgentStack domains currently operate within the Freename ecosystem.

This includes:

* Domain minting

* Resolver-based domain functionality

* Wallet and identity-related integrations supported by Freename-compatible tools

Compatibility with external naming systems, wallets, browsers, and applications may vary depending on resolver support and third-party integrations.

As the broader Web3 ecosystem evolves, additional compatibility or interoperability options may emerge over time. Users should always verify current support directly with the platforms and tools they use.

Disclaimer & Accuracy Notice

This guide is intended for general educational purposes only and reflects the current understanding of the Freename ecosystem and related Web3 naming practices at the time of writing.

Web3 technologies, resolver systems, wallet integrations, and platform features may evolve over time. Users should independently verify important technical, legal, or operational details before relying on any specific configuration or workflow.

AgentStack does not guarantee compatibility with third-party wallets, browsers, applications, or external naming systems unless explicitly confirmed by the relevant providers.

Nothing in this guide should be considered legal, financial, or technical advice.

Need Help?

If you’re unsure how to mint, configure, or use your AgentStack domain, we’re happy to help guide you in the right direction.

AgentStack focuses on Web3 naming infrastructure for AI agents and digital identity use cases within the Freename ecosystem.

We can help with:

✅ General guidance on domain naming strategy

✅ Understanding Freename-based domain workflows

✅ Questions about domain organization and use cases

✅ Feedback on SLD selection and branding ideas

We do not provide legal advice, guaranteed integrations, or custom technical development.

📩 Contact: info@dotai.domains