AI Agent OSGuarded mainnet beta. .rama identity, smart wallets, sponsored gas, permissions and scheduling are available for controlled testing.Open Agent OS
Learning center

Rama Name Service

Governance and Policy for .rama Names

Define organization-level rules for naming, delegation, renewal and disputed identity changes before broad adoption.

In this guide

Practical outcomes

  • Create naming policy
  • Assign administrators
  • Maintain change records

How this works in practice

Define organization-level rules for naming, delegation, renewal and disputed identity changes before broad adoption.

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.

  1. 01. Create naming policy. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
  2. 02. Assign administrators. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
  3. 03. Maintain change records. 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