Uniqueness
One canonical assignment for a number in the selected namespace.
One number. One canonical state.
Many independent resources.
Resolve a memorable number into a durable identity reference, then let websites, apps, wallets and services add their own capabilities without redefining the number.
The spatial chain is an explanatory model. Canonical state and live availability remain owned by the registered Z7 providers.
A narrow chain with a precise job.
The target Z7 blockchain anchors only facts that independent resources must agree on. Content, search indexes and service data remain outside the canonical record.
Control
The current Z7 Wallet assignment and explicitly permitted controllers.
Transitions
Claim, update, delegation, transfer, recovery, suspension and retirement.
Integrity
Versioned references to the active identity manifest and associated content.
History
Traceable state changes without storing every document or interaction on-chain.
Resolve once. Continue in the right context.
Websites, apps, APIs, contacts, wallets and services can start from the same Z7 number without becoming the same system.
Use the coordinate. Keep domain ownership where it belongs.
A resource resolves the number, reads the profile and attaches its own service through registered owner contracts.
- 01INPUT
Z7 number
Accept one compact, language-neutral coordinate.
- 02RESOLVE
Namespace
Resolve the current number state through the Z7 owner.
- 03PROFILE
Public state
Read the profile content without reconstructing ownership.
- 04RESOURCE
Local service
Attach capabilities through the resource and registered extension owners.
Know what each layer can prove.
Z7 keeps network status, profile content, external evidence and resource services readable as separate sources.
The current state of the Z7 number and its canonical reference.
Information published as part of the number profile.
References and attestations whose authority remains external.
Capabilities supplied by the resource currently presenting the profile.
CONCEPT STATUS
Architecture first. Production claims only after proof.
The whitepaper defines a target architecture, not a production protocol. The portal must show that boundary instead of inventing live chain metrics.
OPEN DECISIONS
- Canonical number format and namespace
- Consensus, validators and data availability
- Fees, anti-spam and allocation policy
- Key, delegation and recovery model
- Privacy, attestation and governance rules
LIVE COORDINATES
Explore number profiles
Open real profiles and see how content and connected services are organized around a stable Z7 number.
Put agreement on-chain. Keep experience distributed.
The blockchain carries the minimum shared state. Profiles and resource services can evolve independently while their relation to the number remains verifiable.
Canonical state
- Confirmed claim
- Assigned Z7 Wallet
- Status and state version
- Scoped authority and delegation
- Transfer, recovery and revocation events
- Manifest integrity reference
Content and services
- Names and descriptions
- Images, documents and media
- Search indexes and rankings
- Messages, comments and analytics
- Prices, availability and recommendations
- Resource-local services and interfaces
One number can represent many kinds of identity
The identifier is compact and language-neutral; the subject and its services give it meaning.
People & teamsOrganizationsProductsServicesIdeasPublicationsPlacesCommunitiesDevicesPhysical objectsDigital assetsProjects
{%CTMA:_Z7_NAV_USE_CASES%}Purchase, manage and exchange
NMN connects number acquisition with wallet, exchange and market services.
Buy a number
Choose an available Z7 Number Profile and complete the configured purchase flow.
Explore numbersManage NMN
View balances, transactions and transfers in the wallet area.
Open walletExchange
Acquire NMN from supported currencies through WSPAYMENT.
Open exchangeMarkets
Open the configured monochrome market chart in WSDEX.
Open DEXCANDIDATE → CANONICAL
A displayed candidate is not yet a claimed number.
In the target network model, availability is revalidated when the claim is submitted. Only a valid confirmed claim assigns the number to a Z7 Wallet and creates network-recognized ownership.
Generate
A resource proposes a syntactically valid number.
Revalidate
The current network state is checked at claim time.
Claim
A signed transition requests assignment to a Z7 Wallet.
Confirm
Consensus and finality decide whether the claim becomes canonical.
Activate
Authority, manifest reference and lifecycle controls become effective.
START WITH A NUMBER
Find the Z7 number that fits your identity
Search the namespace, create your account and build a profile that can grow across content, contacts and services.