DIAL Identity — a telco-inspired addressing and identity layer for Canton Network in two layers and two packages. Names and Numbers, issued by Pairpoint, owned by the holder, resolved through a trusted directory, traded on a private marketplace, settled on-chain.
Telcos do not sell phone numbers. They sell identity, addressability, and trust at planetary scale — every E.164 number is a regulated identity primitive backed by KYC, lawful intercept, fraud surveillance, and 150 years of operational discipline.
On-chain, identity is broken. ENS-style handles aren't issued — they're squatted. Wallet addresses aren't names. The few identity products native to Canton today read as engineering primitives, not finished products.
Vodafone/Pairpoint sits on an unfair stack of advantages no Web3-native protocol can manufacture: a regulated issuance authority, a hundred-million-customer KYC backbone, the trust of an institutional brand, and an existing on-chain footprint via Pairpoint on Canton.
DIAL turns that stack into a product.
An enterprise-grade identity layer on Canton Network. Pairpoint issues virtual numbers and human-readable names; users own them, send tokens to them, trade them on a marketplace; agents and devices use the same primitive at B2B scale.
Closest analogue · Telegram virtual numbers × ENS × a Tier-1 telco · all settled on Canton.
adi.dial) and Numbers (+DIAL · 0042 · 8819) that consumers and enterprises own, trade, and send value to. Two layers (Network + App), two packages (Names + Numbers), six revenue lines. The moat isn't the registry — it's who runs it, with what brand, infrastructure, and regulatory posture. On Canton, that's Pairpoint.
Canton is shaping into the institutional settlement network. Identity for that network has to feel institutional. Pairpoint already lives there; this extends the surface.
Stablecoins on telco networks is now a plausible primary settlement layer. Nobody wants to send a 64-character Party ID a hundred dollars.
AI agents are about to transact autonomously. Agents need identities issued by someone with KYC posture. Telcos do that already.
Pairpoint's IoT footprint already addresses hundreds of millions of devices. Putting them on-chain as named identities is incremental, not new.
The window matters. Canton's identity surface is unowned. Whoever ships the identity layer for it first — for consumers, enterprises, and partner registrars alike — will sit on the registrar economics for a decade. Issue first; entrench fast.
DIAL Identity is one product on two layers, sold in two packages. The structure matters more than any single SKU — it's what determines the moat.
The infrastructure layer. Pairpoint provisions on-chain identities on multi-tenant Canton nodes — Sovereign tier for dedicated infrastructure, Omnibus tier for pooled consumer accounts. The DIAL Directory resolves every name and number to its on-chain address.
Honest framing: this layer will commoditize. Banks, custodians, and other infrastructure players will sell similar multi-tenant capability inside 18–24 months. Necessary but not sufficient.
The identity OS. Sits on top of any DIAL-issued account and lets the holder manage every identity inside it — humans, AI agents, IoT devices, sub-entities. Beautiful UX, marketplace, Telegram bot, KYC/KYB tooling, SMS/RCS bridge.
This is the moat. Other multi-tenant providers won't build a polished product layer — they're banks and custodians, not product companies. The App is what differentiates DIAL from every other Canton infrastructure offer.
DIAL Identity sells in two packages. Different aesthetic, different buyer, different commercial model. Sophisticated customers buy both.
Human-readable handles. Hierarchy via subdomains. The format people share, the destination people send to.
.dial · .pair · .point · .vf.caterpillar · .acme · .[org]adi.dial · acme.dial · ceo.caterpillar · trade.vfPhone-number-style identifiers. Hierarchy via prefix + numerical blocks. The telco-native addressing layer for fleets, machines, agents, and SMS/RCS bridge use cases.
+PP · +DIAL · +VF+CAT · +ACM · +TES+DIAL·0042·8819 · +CAT·001·001·01 · +VF·0001·0001An IoT device is an identity. An AI agent is an identity. An employee is an identity. They're all the same primitive — issued under a name (subdomain: meter-7821.acme.dial) or a number (allocation: +CAT·001·001·01) — managed inside the same DIAL App. The Sovereign customer doesn't buy "Agent IDs" and "Device IDs" as separate products. They buy the Network subscription, get the App, and issue whatever identities their operations require.
Format note · DIAL Numbers use a 2–3 letter alphabet prefix (e.g. +CAT, +VF). The alphabet prefix is the structural disambiguator from real telephone numbers — E.164 country codes are digit-only. DIAL Numbers are addressing on Canton, not telephony — different regulatory perimeter.
The Network commoditises. The App is the moat. The packages are the revenue.
Layer 01 splits into two infrastructure tiers. Same App on top, different commercial mechanics underneath. The split decides pricing, custody, and sales motion.
Each enterprise gets its own dedicated, segregated on-chain identity. Pairpoint runs the underlying infrastructure; the client retains exclusive signing rights. Acts as a first-class network participant without operating its own server.
Consumers get a name and number without ever touching keys, hashes, or node configuration. Pairpoint manages the underlying account; users see a clean Vodafone-grade app. Frictionless onboarding wins the volume game.
Higher-balance Omnibus consumers can graduate to Sovereign on request. This is the upgrade path that turns retail customers into enterprise revenue over time.
The DIAL consumer app. Mobile-first. Designed to feel like a Vodafone product first and a wallet second — enterprise-grade trust language, identity at the top, sending as a verb.
Identity-first. The number and name sit at the top — that's the product. The wallet balance is secondary; sending is a verb ("DIAL"), not a UX phase. Recent counterparties are names, not addresses.
Primary issuance. The user types, sees real-time availability, and picks a tier. Pricing follows length: 3-char names are auctioned, 4–6 char are premium, 7+ are standard. Reserved corporate names are blocked entirely until verification.
The send flow is the product wedge. Users send to a name, never to a hash. KYB tag indicates Vodafone-attested business identity — a thing no other Canton wallet can show.
The verb on the CTA is consistently "DIAL" — same metaphor across surfaces. Behind the scenes, every transfer requires recipient consent before settlement, which we surface as a quiet promise ("recipient confirms on receipt") rather than UX friction. Spam-proof by architecture; clean by design.
Secondary trading for NUMBERS and NAMES. Browse, bid, list, transfer. Pairpoint takes a 2.5% fee on every transaction — perpetual revenue from a finite namespace. Premium short numbers, dictionary names, and corporate handles drive the volume.
Unlike public NFT marketplaces, DIAL is privacy-by-default. Bids, balances, and trading strategies stay confidential between counterparties — a meaningful advantage for institutional buyers who don't want portfolios scraped from a public mempool.
Every listing carries a provenance trail, visible inline. Enterprise-grade trust extends to the secondary market.
B2B console. ACME runs DIAL App on top of its private namespace — human agents under .acme, machine identities under +ACM. Bulk issue, scope permissions, monitor balances, watch transaction velocity.
This screen is the killer demo. The Sovereign tier customer doesn't see "agents" and "devices" as separate products — they see one console managing every identity they care about. That's the App moat in one screen.
The DIAL bot. Natural-language send through any messenger surface. The user types "send 50 USDC to acme.dial". The bot resolves, confirms, executes, returns a Canton receipt.
Why Telegram first? It's where Web3 conversation already happens, and the surface is conversational — which is the point. The same bot pattern ships to WhatsApp Business and SMS/RCS in Phase 3 (Vodafone-native, not partnered).
DIAL is only as valuable as the surfaces it shows up on — and the registry that resolves them. Underneath sits the DIAL Directory, a Pairpoint-operated resolver that maps every consumer-friendly name to its on-chain address at the moment of transaction. Whoever runs the directory runs the address book. Four integration tracks layer on top.
A drop-in resolver library. Any Canton wallet integrates the SDK and starts showing adi.dial instead of Alice::1220e7a8…. Reverse resolution included.
Distribution play. Free for partners; the value to Pairpoint is registry pull-through. Whoever resolves names becomes the address book.
Target · 5 wallets in 6 months · including the largest 2 by Canton TVL
Natural language send through @dialbot. Resolves names, confirms intent, executes on Canton, returns a receipt. Optional: receive notifications when funds land at your name.
Why Telegram first: Web3 lives there. Pattern then ports to WhatsApp Business and Vodafone-native SMS/RCS in Phase 3 — that's the unfair-advantage moment.
Stack · Telegram Bot API · OpenAI/Anthropic for parsing · Canton tx submission via Pairpoint node
White-label issuance for other Canton participants. A bank, exchange, or ecosystem brand can issue subdomains under the DIAL registry — user.bankname.vf — with revenue share back to Pairpoint.
This turns DIAL from a Pairpoint product into a registrar economy. Pairpoint becomes the root.
Commercial · 30% rev-share to partner · 70% to Pairpoint · annual renewal logic
The unfair advantage. Vodafone is the only DIAL participant who can settle on-chain transactions via SMS/RCS. Send a USDC payment by texting PAY 50 acme.dial to a Vodafone shortcode.
This is the moment DIAL stops looking like a Web3 product and starts looking like a Vodafone product. Massive distribution lever in emerging markets.
Status · Phase 3 · Requires Pairpoint–Vodafone Group commercial agreement · regulatory review per market
Anyone can build an identity registry on Canton. Almost no one can build this one. Pairpoint's moat is the operating-licence-and-trust stack of the parent telco — assets you can't replicate at any speed.
Vodafone is a regulated telecommunications carrier with E.164 number allocation rights in dozens of markets. The visual format +VF·0042·8819 reads as a real telco identifier, not a marketing skin. No Canton-native competitor can claim this.
Every Vodafone customer is already KYC'd to telecoms-regulator standard. DIAL inherits a verified-identity stream at near-zero marginal cost. Web3-native registrars need to build this; Pairpoint has it.
Vodafone is one of a small number of brands consumers will trust to hold financial keys. The badge "Pairpoint-verified" on a name does work that no on-chain trust signal can match. This is the brand asset, on-chain.
In Phase 3, Vodafone's messaging infrastructure becomes a DIAL surface — sending tokens by SMS/RCS. This is the only on-chain identity product that can credibly ship that integration. Period.
Pairpoint already addresses millions of IoT devices through Vodafone's connectivity. The Device IDs SKU is a re-skin of work already done — bulk identity for endpoints already on Pairpoint's footprint.
Pairpoint is already a recognised participant on Canton. DIAL doesn't ask the network to accept a new entrant; it extends the surface of an entrant the network already trusts. The integration cost across the ecosystem drops to near zero.
Multi-tenant Canton infrastructure will commoditise — banks, custodians, and exchange operators will all sell similar capability. What they won't build is a polished product layer on top. They're financial institutions, not product companies. Pairpoint, with Vodafone DNA, is one of the few entities that can credibly ship the App that turns Canton identities into a product anyone can use. That's the moat.
Every name lookup on DIAL routes through the Pairpoint-operated Directory. Wallets, bots, partner registrars — all of them resolve through us. The Directory is a perpetual toll booth: low-margin per call, immense moat in aggregate, and impossible to replicate without rebuilding the registry from zero.
The product is not the registry. The product is who runs the registry.
Optimised for an early entrenchment of issuance, then layering distribution and B2B revenue on top.
.dial · .pair · .point · .vf for Names; +PP · +DIAL · +VF for Numbers. Mobile app (iOS/Android) with home, claim, send, receive. Pairpoint-managed account abstraction for frictionless onboarding. Sovereign tier infrastructure stood up in parallel for pilot enterprise customers.
@dialbot live on Telegram with NL parsing. Public API for partner registrars.
Six revenue lines, layered. Primary issuance (Names + Numbers) is the land-grab. Renewals, marketplace fees, B2B subscriptions, and partner rev-share are the compounding tail.
| Line | What it is | Pricing |
|---|---|---|
|
DIAL Names
Primary issuance
|
Tiered by length and namespace. 3-char auctioned, 4–6 char priced premium, 7+ standard. .vf namespace priced at premium multiple over .dial. |
29 — 100,000+ USDC (per name) |
|
DIAL Numbers
Prefix + allocations
|
Premium prefix purchase for sovereigns (+CAT, +ACM) is the headline B2B revenue line — entire numeric namespace assigned to the buyer. Plus per-number issuance in public namespaces and vanity numbers. |
Prefix · 50K — 1M+ USDC + per-allocation |
|
Annual renewal
Recurring
|
All issued names, numbers, and prefixes renew annually. Lapses go to public auction with 30-day grace. Holders get reminders via DIAL app. | 15 — 5,000+ USDC / yr (per item) |
|
Marketplace fee
Secondary trading
|
2.5% of every secondary transaction. Both sides on auction settlements. Royalty option for original buyers in vanity tiers. | 2.5% (per tx) |
|
Sovereign tier
Network subscription
|
Annual subscription per enterprise for dedicated, segregated on-chain infrastructure. Includes a base allocation of identities, attestation hooks, KYB review, and SLA. Per-agent / per-device pricing layered on top for IoT and agent fleets at scale. | $5K — $100K+ / yr + $2–50 / unit |
|
Partner registrar
Rev-share
|
Banks, exchanges, brands run their own namespaces under the DIAL Directory. Pairpoint takes 70% of partner-registrar revenue. | 70% rev-share (of partner takings) |
Note: DIAL is intentionally a both-sides-of-the-flywheel model. Primary issuance pays for distribution; distribution drives marketplace volume; marketplace volume drives renewals and partner registrars. Each line feeds the next.
.vf mocked here — final suffix needs Vodafone brand sign-off. .dial, .pairpoint, or unsuffixed are alternates.