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

.rama Name Pricing and Registration Costs

Present registration and renewal costs transparently and distinguish name-service charges from normal Ramestta network gas.

In this guide

Practical outcomes

  • Show full cost
  • Estimate gas
  • Avoid misleading checkout

How this works in practice

Present registration and renewal costs transparently and distinguish name-service charges from normal Ramestta network gas.

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. Show full cost. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
  2. 02. Estimate gas. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
  3. 03. Avoid misleading checkout. 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