01
Identity
Give addresses a human layer.
A readable name can represent a person, product or service without asking every user to work from a raw address.
Rama Name Service
A readable identity for the Ramestta network.
RNS turns an address into a .rama name that people, products and controlled agents can use and recognize. Register and manage names through the live Rama Name Service application.
Human-readable namesUse a .rama identity instead of repeatedly sharing a long address.
Owner-controlled recordsManage the resolved address and lifecycle from the RNS application.
Names that can scaleSet up subdomains under a registered .rama name when the product needs a namespace.
The RNS flow
One name. A clear route to the right onchain identity.
RNS is the network-facing identity layer. The registration application handles name search and management, while the rest of the Ramestta stack can point users and agents to a stable, readable identifier.
- 01
Search
Check a label and review its current availability.
- 02
Register
Choose the registration term and complete the wallet transaction in RNS.
- 03
Resolve
Set or update the address that the .rama name resolves to.
- 04
Extend
Renew, transfer or create subdomains as the identity grows.
Identity flow
A .rama name starts in RNS and becomes useful across the ecosystem.
Rama Name Service manages name ownership and address records. The same readable identity can then be used as the entry point for payment destinations, products and controlled agent workflows.- RNS
Search a .rama name
Check availability through Rama Name Service before registration.
- Ownership
Register with a wallet
The owner controls the name lifecycle through the live RNS application.
- Resolution
Point to an address
Set the resolved address that the readable .rama identity represents.
- Use everywhere
Share one readable identity
Apps, payments and controlled agents can reference the same human-readable identity layer.
What RNS is, visually
One human-readable name, used everywhere on Ramestta
RNS replaces a long 0x… address with a name you can read and remember — like yourname.rama. You register it once with your wallet, point it at an address, and the same identity works across the ecosystem: receiving payments in RamaPay, naming an AI agent, or signing into apps and profiles. Global use cases include creator handles, business payment addresses, wallet-friendly usernames, and machine-readable identities for autonomous agents.
Built for the full stack
Identity that travels with the rest of the stack.
A .rama name is useful when it connects people and applications to payments, developer products and controlled agent workflows.02
Payments
Make payment destinations clearer.
Pair a .rama identity with the RamaPay experience to make a recipient easier to recognize before value moves.
03
Agents
Start controlled agents with an identity.
Agent OS uses .rama as the readable identity component alongside an owner relationship, smart wallet and explicit controls.
Live RNS capabilities
The live app owns registration and name management.
Search before you register
Check whether a label is available, then open the verified registration flow for the corresponding .rama name.
Resolve a name to an address
Use a readable .rama name as an identity layer over the wallet address it resolves to.
Manage the lifecycle
The live manager supports renewal, ownership transfer and updating the address associated with a registered name.
Create a namespace
Registered names can create subdomains for teams, products, wallets or purpose-specific identities.
For builders and agents
Use identity as a primitive, not a profile field.
For Agent OS, a .rama name is a discoverable identity alongside the controller, smart wallet, permissions and messaging keys. It does not remove the need for explicit limits or approvals.