G

Overview

Overview

Gao Domain — Identity Layer Protocol#

Role in Gao Internet Architecture#

Gao Domain operates within the Gao Internet 8-layer stack:

1.	Workspace — Operations Interface

	2.	Browser — Gateway Layer

	3.	SDK — Developer Layer

	4.	Payment — Settlement Layer

	5.	Domain — Identity Layer <—— This layer

	6.	Network — Transport Layer

	7.	DePIN — Infrastructure Layer

	8.	AI OS — Intelligence Layer

Gao Domain provides the identity foundation consumed by all other layers.

Ownership Model — Permanent, One-Time Claim#

Gao Domain uses a permanent ownership model:

  • Domain is claimed once via on-chain mint

  • No renewal fee — ownership is perpetual

  • Ownership is recorded on Ethereum (post-snapshot finalization)

  • Transfer requires a valid cryptographic signature from the current owner

  • Gao has no unilateral authority to revoke, reassign, or expire a domain

This model reflects Web3 identity principles: once claimed, the domain is a permanent on-chain asset owned exclusively by the key holder.

Ownership Record Structure

domain: shop.gao
owner_address: 0xabc...
chain: Ethereum
mint_block: 21xxxxxx
transfer_count: 0
lock_status: false

Ownership Lifecycle

AVAILABLE
    │
    ▼ (mint transaction)
ACTIVE
    │
    ├──▶ LOCKED (optional, owner-set)
    │
    └──▶ TRANSFERRED (signature required)

There is no EXPIRED state. Domains do not expire.

Identity Container Concept#

Each Gao Domain is a programmable identity container.

Example:

alice.gao
├── wallet_eth:   0xabc...
├── wallet_sol:   9sd...
├── wallet_tron:  T98...
├── endpoint:     https://api.alice.gao.global
├── agent:        assistant.alice.gao
├── metadata:     { name, avatar, description }
└── subdomains:   [shop.alice.gao, support.alice.gao]

Endpoints are optional and defined by the domain owner.

Identity records are owner-signed and on-chain verifiable.

Identity Scope#

A Gao Domain may represent:

Entity Type

Example

Individual

alice.gao

Business

shop.gao

Organization

dao.gao

AI Agent

assistant.shop.gao

Service

payment.shop.gao

Device (DePIN)

sensor.factory.gao

This flexible model supports the full range of Gao ecosystem applications.

Core Functions#

1. Identity Anchor

A Gao Domain (merchant.gao) represents:

  • A cryptographic identity

  • Owner-controlled authority

  • Multi-layer interoperability

Ownership is determined solely by key control. Gao does not custody domains.

2. Multi-Chain Wallet Mapping

Domains resolve to multiple blockchain addresses.

merchant.gao →

ETH:    0xabc...
SOL:    9sd...
BASE:   0xdef...
TRON:   T98...

Properties:

  • Owner-signed updates only

  • On-chain verifiable

  • Fully auditable

  • Lockable by user

Gao cannot modify mappings without owner signature.

3. Agent Binding Model

AI agents operate under domain authority.

merchant.gao
├── Owner Key
└── Agent Keys (scoped)
    ├── assistant.merchant.gao  [read, respond]
    ├── booking.merchant.gao    [read, write:calendar]
    └── payment.merchant.gao    [read, initiate:payment]

Agent permissions are:

  • Explicitly granted by owner

  • Expirable

  • Revocable

  • Scope-limited

Agents cannot override owner authority.

4. Payment Resolution

When sending to merchant.gao:

1. Domain resolves via Gao resolver
2. Wallet address retrieved for target chain
3. Payment layer (Gao Payment) verifies compatibility
4. Settlement executed
5. Receipt generated on-chain

Gao Domain does not:

  • Custody funds

  • Execute transfers

  • Hold balances

It is a resolution layer only.

5. Service Endpoint Resolution

Domains may resolve to service endpoints.

resolve("shop.gao") →

payment_api:    https://pay.shop.gao.global
booking_api:    https://book.shop.gao.global
support_agent:  assistant.shop.gao
crm_endpoint:   https://crm.shop.gao.global

Applications can auto-discover services through domain resolution.

6. Device Identity (DePIN)

Devices may operate under domain identities.

sensor.factory.gao
camera.home.gao
node.depin.gao
relay.network.gao

Device identities enable secure, verifiable communication between DePIN infrastructure components and applications.

Domain Resolution Architecture#

Resolution Paths

Gao Domains resolve through two paths:

Path A — Gao Browser (Native)

Native resolution within the Gao Browser. No DNS dependency.

User types: shop.gao
        │
        ▼
Gao Browser resolver
        │
        ▼
On-chain identity record (Ethereum)
        │
        ▼
Returns: wallet / endpoint / metadata

Path B — Gateway (External Access)

For access from standard Web2 browsers via the global gateway:

User accesses: shop.gao.global
        │
        ▼
Gao Gateway (gao.global)
        │
        ▼
Resolves → shop.gao identity record
        │
        ▼
Proxies to registered endpoint

Gateway URL pattern:

{name}.gao.global

Example:

shop.gao.global
alice.gao.global
assistant.shop.gao.global

Note: Gateway access requires the domain owner to configure a service endpoint. Domains without an endpoint resolve identity records only.

Subdomains & Identity Graph#

Subdomain Namespace

Domain owners control their subdomain namespace.

shop.gao
├── assistant.shop.gao
├── payment.shop.gao
├── support.shop.gao
├── booking.shop.gao
└── sensor.shop.gao

Subdomains allow organizations to structure services, agents, and devices under a single domain identity.

Subdomain records are:

  • Owner-signed

  • Independently resolvable

  • Inheritable from parent domain authority

Identity Graph

Domains form relationships with other identities.

shop.gao
├── owner       → alice.gao
├── agent       → assistant.shop.gao
├── payment     → payment.shop.gao
├── device      → sensor.shop.gao
└── org         → dao.gao

Applications may traverse the identity graph to discover relationships between entities.

Agent Discovery

Applications may query subdomains to discover AI agents:

resolve_agents("shop.gao") →

[
  assistant.shop.gao,
  sales.shop.gao,
  support.shop.gao
]

This enables automated service and agent discovery.

Ownership & Recovery Model#

Ownership

Ownership requires:

  • Cryptographic key control

  • On-chain Ethereum registry state

  • Valid signature for any update

Governance cannot override private ownership.

Recovery

Recovery options may include:

  • GaoKey multisig

  • Guardian-based recovery

  • Time-delayed ownership transfer

Important:

  • Recovery is user-configured

  • Gao does not custody recovery keys

  • Recovery is cryptographically enforced

  • No recovery bypasses owner-defined rules

  • All recovery actions generate on-chain audit records

Gao has no unilateral recovery authority.

Economic Model#

Domain registration is a one-time utility transaction.

Registration grants:

  • Permanent on-chain identity ownership

  • Access to the full Gao identity stack

  • Subdomain creation rights

  • Agent binding rights

  • Wallet mapping rights

  • Service endpoint configuration rights

  • Secondary market transfer rights

Registration does NOT create:

  • Ownership of protocol revenue

  • Dividend rights

  • Yield mechanisms

  • Guaranteed appreciation

Anti-Speculation Clarification

Gao explicitly does NOT:

  • Market domains as investment assets

  • Promote domain flipping or speculation

  • Guarantee secondary market liquidity

  • Endorse resale price appreciation

Domain registration is a utility function — granting access to identity and infrastructure services. It is not an investment activity.

Governance Model#

Protocol-level governance is:

  • Contribution-weighted

  • Non-token-weighted

  • Time-locked

  • Parameter-bounded

Governance cannot:

  • Reassign private domains

  • Override ownership signatures

  • Modify personal mappings

  • Revoke or expire domains

Ownership authority remains private and permanent.

Security Principles#

Principle

Description

Non-custodial

Users maintain full key control

Signature-required

All identity updates require owner signature

Optional lock

Owners may lock domain against transfers

Time-delayed changes

High-impact changes support optional delay

Agent scope isolation

Agent keys are scoped, cannot escalate

Full audit trail

All state changes are on-chain verifiable

Recommended protections:

  • Hardware wallet for key storage

  • Multisig for business domains

  • Recovery delay configuration

  • Regular agent permission audit

Interoperability#

Gao Domain integrates natively with every layer of the Gao Internet stack:

Layer

Integration

Gao Payment

Domain as payment alias, wallet resolution

Gao Network

Domain-based routing

Gao DePIN

Device identity, node identity

Gao AI OS

Agent governance, agent authority scoping

Gao Workspace

UI identity, account binding

Gao Browser

Native domain resolution (no DNS)

Gao SDK

Developer APIs for resolution, registration, record management

Developer Integration#

Resolve a Domain

import { GaoDomainResolver } from '@gao/sdk';

const resolver = new GaoDomainResolver();

const identity = await resolver.resolve('shop.gao');
// Returns: { wallets, endpoints, agents, metadata }

Resolve Wallet Address

const address = await resolver.getWallet('shop.gao', 'ETH');
// Returns: "0xabc..."

Resolve Service Endpoint

const endpoint = await resolver.getEndpoint('shop.gao', 'payment');
// Returns: "https://pay.shop.gao.global"

Discover Agents

const agents = await resolver.getAgents('shop.gao');
// Returns: ["assistant.shop.gao", "support.shop.gao"]

Full SDK reference: [Gao SDK — Developer Layer]

Not Investment Advice

This document is informational only. It does not constitute:

  • Investment advice

  • Financial recommendation

  • Legal counsel

  • Offer of securities

Risk Considerations

Participation involves:

  • Technical risk

  • Smart contract risk

  • Regulatory uncertainty

  • Market liquidity variability

No guarantees are provided regarding resale value, adoption level, or ecosystem growth.

Jurisdictional Responsibility

Users are responsible for:

  • Compliance with local laws

  • Understanding digital asset regulations

  • Consulting professional advisors

DNS Compatibility Notice

Gao Domains function as identity records within the Gao Internet ecosystem. They are not ICANN-registered DNS domains. Resolution from standard browsers requires use of the Gao Gateway (name.gao.global) or the Gao Browser native resolver.