Rama Name Service
What Is Rama Name Service?
Learn how Rama Name Service gives users, applications and AI agents readable .rama identities on Ramestta.
In this guide
Practical outcomes
- Understand .rama names
- Choose identity use cases
- Resolve a name
How this works in practice
Learn how Rama Name Service gives users, applications and AI agents readable .rama identities on Ramestta.
RNS maps a readable .rama name to onchain records such as wallet addresses, ownership and service metadata. Applications should resolve the name, validate the returned records and clearly show the final destination before a user acts.
Implementation sequence
Turn the topic into a controlled implementation rather than a one-off transaction. Each step below should leave evidence a teammate, user or auditor can independently review.
- 01. Understand .rama names. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
- 02. Choose identity use cases. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
- 03. Resolve a name. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
Evidence to retain
A reliable resolution flow can show the requested name, resolver source, resolved address, current owner where appropriate and the transaction or record state that supports the result.
Control point
A readable name is not proof on its own. Protect against stale records, misleading display names, expired registrations and resolver changes by validating onchain data and retaining a clear address fallback.
Related guides
Register a .rama Name
Follow the lifecycle for checking availability, registering a .rama name and confirming ownership.
Renew a .rama Name
Understand renewal timing and how to maintain a readable Ramestta identity before expiration.
Transfer a .rama Name
Learn how name ownership transfer should be handled, verified and recorded before changing control.