Community Identity Infrastructure

Your community
needs a layer.

Every Discord server, every niche, every movement — when they go blockchain-gated, whoever holds the parent domain mints the future. Name.Guide finds your layer.

live minting →
Chapter 01 — The Community

Your people are
already assembled.

Gaming guilds. Music collectives. Health networks. Faith communities. Investment clubs. Millions of Discord servers, Telegram groups, and online communities exist today — organized, active, identity-ready, but anchored to platforms they don't own.

When these communities go blockchain-gated — and the infrastructure is arriving — they'll need a parent identity domain that all members can mint beneath. That parent is a .tribe domain. The question is: who holds it?

nexus-gaming · 12,847 members
# general
# strategy
# tournaments
# web3-gating
Online — 3,241
J jay.nexus
A alex.nexus
S sarah.nexus
◈   Blockchain gating activated — member IDs minting
Chapter 02 — The Architecture

L1 stays in
custody.
You own L2.

The L1 root domain — gaming.tribe, music.tribe, health.tribe — is held in permanent custody by the Sourceacle trust architecture. It is never sold.

Your community claims an L2 slot beneath it. That L2 is your parent identity — the domain your server, your brand, your DAO mints under. Then your members mint L3 identities beneath you.

You don't need to own the infrastructure. You need to own your layer.

gaming L1 root
tribe TLD
Custody · Never sold
nexus L2 community
gaming L1 root
tribe TLD
Your Layer
jay L3 member
nexus L2 community
gaming L1 root
tribe TLD
Member ID
alex L3 member
nexus L2 community
gaming L1 root
tribe TLD
Member ID
sarah L3 member
nexus L2 community
gaming L1 root
tribe TLD
Member ID
Chapter 03 — The Mint

Members mint.
The tree
grows itself.

Once your community holds its L2, every member can mint an L3 identity beneath it. No central registry. No admin overhead. The Sourceacle principal chain handles trust propagation automatically — your L2 authority flows down to every member ID you authorize.

The community grows; the namespace grows with it. Every new member strengthens the value of the L2 parent you hold.

nexus L2 parent
. gaming L1 root
. tribe TLD
HELD ✓
jay member
. nexus community
. gaming root
. tribe TLD
MINTING...
alex member
. nexus community
. gaming root
. tribe TLD
MINTING...
sarah member
. nexus community
. gaming root
. tribe TLD
MINTING...
marcus member
. nexus community
. gaming root
. tribe TLD
MINTING...
The Three Layers

Find your lane.

.tribe
Community Parent Identity
You are the server owner.
Own the parent domain.
Your Discord has thousands of members. When it goes blockchain-gated, you need a parent .tribe domain that all member IDs mint beneath. L1 is held in custody. You claim L2. Your members mint L3. The hierarchy is self-governing from there.
gaming.tribe · L1 root · in custody
music.tribe · L1 root · in custody
health.tribe · L1 root · in custody
crypto.tribe · L1 root · in custody
.pbdx
Blockchain Wallet Address
Your wallet, your agent,
in plain language.
Public/Private Blockchain Domain Extension. Your .pbdx name replaces a 42-character hex string. Send crypto, run AI agents, and transact on-chain under a human-readable identity. ERC-721 owned. Polygon-native. Available via Unstoppable Domains.
yourname.pbdx · wallet address
yourbrand.pbdx · business identity
agent.pbdx · AI agent ID
nexus.pbdx · enterprise root
.onchain
Trust & Verification Layer
Reputation, credentials,
and agent trust rails.
The .onchain registry handles verification-critical infrastructure — agent identity, KYC, reputation scores, license issuance, and credential records. If your use case is about proving something is true on-chain, this is your layer.
agentverification.onchain · AI trust
reputation.onchain · scores
kyc.onchain · compliance
license.onchain · credentials
Claim your
layer.

The parent domain for your community exists. The question is whether you hold it before someone else does.

N
Name.Guide Discovery
online · powered by Sourceacle