DomainValuation.site

The New Generation of Domain Valuation

Including Blockchain Domain Valution

Domain-Based Payments for Web2 and Web3

1. Overview

EDEBIT is a non-custodial payment abstraction layer that allows human-readable domain names to be used as payment identifiers, while actual settlement continues to occur on existing blockchain and traditional payment rails.

EDEBIT does not replace blockchains, wallets, or payment networks. Instead, it provides a resolution and routing layer that maps a domain name to one or more underlying payment endpoints, depending on context, currency, and user preference.

The system is designed to:

  • reduce user error,

  • improve payment UX,

  • preserve user custody,

  • and remain compatible with existing infrastructure.

2. Core Design Principles

2.1 Non-Custodial by Default

EDEBIT does not hold user funds and does not require custody of private keys.
Users retain full control of their wallets, accounts, and assets.

2.2 Human-Readable Addressing

Domain names act as payment aliases, not wallets themselves.
The domain resolves to one or more destination endpoints (on-chain or off-chain).

2.3 Rail-Agnostic Payments

EDEBIT does not mandate a single blockchain, token, or payment network.
It supports multi-rail routing, including:

  • blockchain networks,

  • stablecoin rails,

  • fiat on-ramps and off-ramps.

2.4 Progressive Decentralization

The architecture supports decentralization where practical, while allowing centralized components where required for performance, compliance, or interoperability.

3. High-Level Architecture

At a high level, EDEBIT consists of five layers:

  1. User Interface Layer (Web2/Web3 Front Ends)

  2. Domain Resolution Layer

  3. Routing & Logic Layer

  4. Settlement Layer

  5. Optional Intelligence Layer (Automation & Optimization)

Each layer is modular and can evolve independently.

4. Domain Resolution Layer

4.1 Domain Ownership

Domains within the EDEBIT ecosystem (e.g., merchant.edebit) represent identity and intent, not custody.

Domain ownership is cryptographically verifiable via:

  • blockchain-based domain registries (e.g., Handshake-style ownership),

  • or registrar-backed records linked to verifiable wallets.

4.2 Resolver Records

Each domain can publish resolver records, similar in concept to DNS or ENS records, but payment-focused.

Examples of resolver records:

  • PAY_USDC_POLYGON → 0x...

  • PAY_USDT_BSC → 0x...

  • PAY_FIAT_EUR → IBAN / PSP reference

  • META_MERCHANT → JSON metadata

  • WEB2_FALLBACK → https://merchant.site/pay

Resolver data can be:

  • on-chain (for transparency),

  • off-chain (for performance),

  • or hybrid (hash-anchored for integrity).

5. Routing & Payment Logic

5.1 Context-Aware Routing

When a payer enters a domain (e.g., shop.edebit), the system evaluates:

  • selected currency or asset,

  • payer wallet capabilities,

  • merchant preferences,

  • regulatory constraints,

  • network fees and latency.

The routing layer then selects the best available settlement path.

5.2 No Mandatory Token Dependency

EDEBIT does not require the use of a proprietary token for basic payment routing.

Optional tokens may be used for:

  • fee optimization,

  • staking access to premium features,

  • governance,

  • or incentive alignment.

6. Settlement Layer

Settlement occurs directly on existing rails, such as:

  • blockchain transfers (stablecoins, native tokens),

  • payment service providers,

  • on-ramp/off-ramp partners.

EDEBIT does not intermediate or re-custody funds during settlement.

6.1 Example Flow (On-Chain)

  1. User enters merchant.edebit

  2. Resolver returns supported payment endpoints

  3. Wallet executes a standard on-chain transfer

  4. Settlement finalizes on the target network

6.2 Example Flow (Hybrid)

  1. User enters merchant.edebit

  2. Resolver routes to fiat on-ramp

  3. PSP handles compliance and settlement

  4. Merchant receives funds via existing rails

7. Intelligence & Automation Layer (Optional)

An optional logic layer can be added to optimize outcomes without controlling funds.

Possible functions:

  • dynamic rail selection (fees, speed),

  • stablecoin preference matching,

  • compliance routing by jurisdiction,

  • automated invoicing or reconciliation,

  • analytics and reporting.

This layer can be:

  • rules-based,

  • API-driven,

  • or AI-assisted,
    without changing custody or settlement guarantees.

8. Security Model

8.1 Threat Model

EDEBIT assumes:

  • users control private keys,

  • blockchains provide settlement security,

  • resolution data must be tamper-resistant.

8.2 Protections

  • Cryptographic domain ownership

  • Signed resolver records

  • Optional hash anchoring on-chain

  • No centralized honeypots of funds

Because funds are never pooled, systemic risk is reduced.

9. Compliance & Integration Considerations

EDEBIT is designed to integrate with:

  • KYC/AML-compliant payment providers,

  • regulated on-ramps and off-ramps,

  • jurisdiction-specific compliance tooling.

Compliance is handled at the rail level, not forced into the domain layer.

10. Developer Integration

10.1 APIs

Developers can integrate via:

  • resolver lookup APIs,

  • payment routing APIs,

  • metadata and analytics endpoints.

10.2 Wallet Compatibility

Wallets can integrate EDEBIT by:

  • resolving domains to standard addresses,

  • executing standard transactions,

  • without protocol-level changes.

11. Why Domains as Payment Identifiers?

Domains provide:

  • human readability,

  • global uniqueness,

  • portability across platforms,

  • brand alignment,

  • and long-term persistence.

EDEBIT uses domains as an abstraction layer, not as a replacement for existing payment infrastructure.

12. Summary

EDEBIT is best understood as:

A domain-based payment resolution and routing layer that sits above existing payment rails, preserving custody while improving usability.

It does not attempt to replace:

  • wallets,

  • blockchains,

  • banks,

  • or payment processors.

Instead, it connects them through a consistent, human-readable interface that can evolve alongside both Web2 and Web3 ecosystems.





Web 3 and Agentic AI

Bringing in a New Era

Starter Dual Stack Offers By GTIN Token Limited

(Owners and operators of the Web-3 and the AgenticAI TLDs)

What is Web3?

Web3 is the new Iteration of the Internet. Web 1 was the internet of Information, an Internet of Static web pages. Web 2 evolved into the transactional Internet, and the Internet of social Media. Web 3 is the Internet that facilitates the transfer of value by tokenizing items of value.

What is Agentic AI?

Agentic AI consists of AI agents that mimic human decision-making, to solve problems in real time. In a multiagent system, each AI Agent performs specific tasks, to reach specific goals, as part of a team. Their efforts are coordinated through AI orchestration

What Are Agentic AI Sites?

Agentic AI sites are websites (or endpoints) that don’t just display information—they act on a user’s behalf. They are built around AI agents that can understand intent, make decisions, query tools or other sites, and return results or take actions automatically. In simple terms, a normal website answers questions. An Agentic AI site gets things done. So in summary:

Web 1:  Pages Web 2:  Platforms Web 3:  Tokenized Identities

AI Era: Agents + Endpoints (Agentic AI sites sit at this last layer)

The Web3 + Agentic AI Advantage

Web3 → stable, facilitates direct transfer of value
Agentic AI → decision and routing
Together → AI-native infrastructure



A Macro Shift

We are entering a post-search internet. Users increasingly interact with AI agents, not search engines. AI agents don’t browse pages — they route intent to trusted endpoints.

This fundamentally changes where value accrues online.



  • Web3 provides the identity layer.

  • Agentic AI provides the decision layer.

     

Prime Web2/Web3 Domains Dual Stack Domains bridge from the familiar Web2 that everyone knows to Web3 and so help to utilize Web3. We are using Template.Direct/Template.1 as an example of a Dual Stack Template. Please see https://template.direct



How Web3 Helps Agentic AI

1. Stable, Portable Identity

Web3 domains provide:

  • persistent identity

  • cryptographic ownership

2. Endpoints, Not Pages

Web3 domains naturally function as:

  • endpoints

  • identifiers

  • routing targets

This matches how AI agents operate.

3. Machine-Readable by Design

Web3 ecosystems normalize:

  • structured metadata

  • resolver logic

  • predictable interfaces

This lowers friction for AI agents.

How Agentic AI Helps Web3

1. AI Makes Web3 Usable

Most users don’t want:

  • wallets

  • technical setup

  • protocol complexity

AI agents take the complexity away.

2. AI Drives Discovery Without SEO

  • Web3 projects struggle with visibility.

  • Agentic AI routes users directly to endpoints, bypassing SEO entirely.

3. AI Turns Domains into Interfaces

In an agentic world:

  • domains are not destinations

  • they are instructions

AI agents use Web3 domains instead of asking users to understand them.

4. AI Creates Demand for Prime Generic Domain Names



As agents choose endpoints automatically:

  • naming clarity becomes valuable

  • short, semantic domains outperform

  • identity means more than content

     

This directly increases the value of well-positioned Web3 domains like Shops.1.



What “Agentic” Means

An AI agent is an AI system that can:

  • interpret a goal (not just a keyword),

  • decide what steps are needed,

  • call tools, APIs, or other endpoints,

  • and return a result or take an action.

     

An agentic AI site is therefore a site that is:

  • goal-driven, not page-driven,

  • endpoint-oriented, not document-oriented,

  • interactive and autonomous, not static.

How Agentic AI Sites Differ from Traditional Websites



Traditional Website

Agentic AI Site

Pages & menus

Goals & actions

User clicks links

AI decides next step

SEO-driven

Intent-driven

Human-only

Human + AI agents

Reads data

Acts on data



- A Traditional site assumes a human is browsing.
- An Agentic AI site assumes an AI may be the visitor.



3. Core Components of an Agentic AI Site

3.1 An AI Agent Layer

This is the “brain” that:

  • interprets user or agent queries,

  • reasons about intent,

  • decides which tools or endpoints to call.



Human Interface

Most agentic AI sites will provide:

  • a normal web UI for humans,

  • transparency about how results are generated,

This creates a dual audience: humans and machines.



Why Agentic AI Sites Matter Now

Users Are Skipping Search



People increasingly say:

  • “Find me a shop that sells…”

  • “Where should I buy…”

  • “Show me trusted sellers…”

They expect answers, not links.

AI Needs Endpoints, Not Pages

AI agents want clear endpoints, Agentic sites are built for AI consumption.

Why Domains Become Important in Agentic AI

In an agentic world:

  • a domain becomes an identity,

  • an API surface,

  • and an anchor.

This is why names like Shops.1 matter:

The name tells the AI what this endpoint is for.

That semantic clarity improves routing,recall, and trust weighting.

Prime Web3 domains have a lot of importance in the current era for reasons that include:



1) The AI era shifts value from content to coordination points

2) Prime Web3 domains become routing endpoints, not websites

3) AI systems prefer canonical names over brands

4) Dual Stack architecture unlocks monetisation without trust erosion

5) Prime Web3 domains behave like digital land, not software

6) Agentic AI turns domains into services by default.

7) The “.1” pattern signals root-level authority

8) Prime domains are option-rich assets

9) Prime domains benefit from AI-driven winner-take-most dynamics

10) Web3 domains add cryptographic hooks unavailable to Web2 domains

 

1) How AI Agents Decide Which Sites to Trust

AI agents do not “trust” sites the way humans do.
They evaluate signals, structure, and predictability.

They think of trust as a weighted score, not a binary yes/no.

Voice & Personal Assistants like Amazon Alexa are  agentic systems, even if users don’t always think of them that way

Identity & Naming Signals (Very High Weight)

AI agents heavily favour sources that have:

  • Clear semantic naming
    (e.g.     Shops.1 clearly implies “shops”)

  • Stable, canonical endpoints
    (a consistent domain that always represents the same function)

     

Why this matters:

AI agents route intent. Names help them decide where intent should go.

This is why short, category-defining, non-ambiguous domains perform disproportionately well in agent routing

Conceptual Comparison

- Search Engines (Web 2 Model)

User → keywords → ranked links → browsing → decision

  • SEO-driven

  • Ad-biased

  • User does the work

  • Pages matter more than outcomes

Weakness: Does not scale to conversational or intent-based queries.

- Marketplaces (Platform Model)

User → platform → listings → platform checkout

  • High trust

  • High control

  • Seller lock-in

  • Platform owns discovery

Weakness: Sellers don’t own identity or future discovery.

- Agentic AI (Post-Search Model)

User intent → AI agent → trusted endpoints → action

  • Intent-driven

  • Outcome-focused

  • Endpoint-based

  • Platform-agnostic

     

Strength: AI chooses where to go — not just what page to show.

1) Compressed 10-Slide Investor Deck

Shops.1 — The AI-Native Commerce Routing Layer

In Summary

Search is being bypassed.

  • Users ask AI, not search engines

  • AI agents route intent, not links

  • Value shifts from pages to endpoints

The Problem

Discovery is broken for the AI era.

  • Search = noisy, ad-driven, SEO-gamed

  • Marketplaces = closed, seller lock-in

  • Sellers lack AI-native, portable identity

The Opportunity

AI agents need trusted endpoints.

They prefer clear naming and structured data

Why Now?

  • AI agents becoming default interface

  • Search losing relevance

  • Endpoints being established now

Early defaults win long-term.

The Future

In a post-search internet, branded endpoints win.

e.g. Shops.1 can becomes the default commerce endpoint AI agents trust.



The Starter Dual Stack Agents being offered

Starter Agents combine:

  • A premium Web3 domain

  • A Web2 twin site

  • A pre-configured Agentic AI capability

They are designed to:

  • demonstrate real utility,

  • seed the agent ecosystem,

  • and help early adopters build first-mover advantage.

Why Are These Discounted?

These offers exist to:

  • populate the agent network,

  • train AI routing behavior,

  • establish endpoints early.

Once the starter agents are in use, pricing changes.

What You Get

✔ A premium agentic Web3 domain
✔ A dual stack Web2/Web3 presence
✔ A starter AI agent with defined capabilities
✔ Future upgrade paths



How do I get a Starter Dual Stack?



Please visit https://agenticai.website/starter-dual-stack



MoneyBack Guarantee and Option to pay in Instalments/Get Financing



Purchasers get a full 60 Day Moneyback Guarantee. Invoice and Payment by Paypal gives full Buyer Protection, and the Opportunity to pay in 3 equal instalments, or get financing over 2 years

 

 

 

. Commercial Terms (Proposed)

Term Length

  • Initial term: 3 years

  • Renewal: automatic by mutual agreement

Revenue Share (Network-Derived Revenue)

Applies to revenue generated from Web-3 Network tenants and partners:

  • 70% Operator

  • 30% Web-3 Network

This reflects:

  • operator responsibility for build, hosting, compliance, and support,

  • Web-3 Network contribution of domain, distribution, and ecosystem.

Independent Revenue

  • 100% retained by the Operator

  • Applies to all non-network clients, products, and services

Minimum Operator Obligations

The operator must:

  • Maintain uptime ≥ 99.5% (rolling 30 days)

  • Provide dashboards and reporting for all core network TLDs

  • Support onboarding for new network tenants

  • Maintain GDPR-compliant data handling

  • Provide quarterly performance summaries to the Web-3 Network

Network Obligations

The Web-3 Network will:

  • Designate ANALYTICS.1 as the official analytics endpoint

  • Promote analytics usage across its ecosystem

  • Avoid operating a competing analytics platform

  • Provide reasonable notice of major network changes

Exit / Termination

Either party may terminate if:

  • material breach remains uncured after notice,

  • prolonged service failure occurs,

  • insolvency or abandonment is evident.

On termination:

  • operator retains independent analytics business,

  • network retains domain stewardship and data continuity rights.