/Docs/Rama Name Service/RNS Overview

Rama Name Service

.rama identitiesMainnet registry

Rama Name Service (RNS) maps memorable .rama names to Ramestta addresses and records. It makes account, application and agent identities easier to verify, share and integrate than raw hexadecimal addresses.

What an RNS name can represent

◈

Wallet identity

Resolve a name such as ramestta.rama to its current wallet address.

◉

Agent identity

Give an autonomous service a readable, persistent identity separate from its controller.

▤

Application records

Attach text records or endpoints that an application can validate and display.

⌘

Primary name

Associate a preferred reverse identity with an address where supported by the resolver.

Registry model

LayerResponsibility
RAMANameService registryRegisters, renews, transfers and resolves flat .rama names
Resolver recordsReturns the address and supported text records for a name
RamaScan indexerIndexes registrations and exposes name lookup through explorer APIs
Wallets and appsResolve names before display, transfers, messaging or agent setup

Safe name management

  1. Register a name from the approved RNS interface or contract flow.
  2. Verify the target address before setting or transferring a record.
  3. Use a multisig-controlled address for protocol, treasury or production names.
  4. Store recovery and ownership procedures outside the application UI.
  5. Validate the resolved address in a trusted wallet or RamaScan before sending assets.
â„šī¸Fresh registry
The current RNS registry is indexed on RamaScan for forward lookups. Applications should treat a resolved address as the source of truth and never rely on display text alone for authorization.

Found an issue with this page? Report on GitHub