/Docs/Rama Name Service/Resolution & Integration

RNS Resolution and Integration

Applications should resolve a .rama name before preparing a transfer, associating an agent identity or displaying an account. The resolved address must be checked with normal address-validation rules.

Recommended resolution flow

  1. Normalize the user-entered name and confirm it uses the .rama suffix.
  2. Query the RNS resolver or RamaScan name-service API.
  3. Validate that the returned value is a valid EVM address.
  4. Show both the human-readable name and a shortened address to the user.
  5. Use the resolved address for the transaction; retain the name only as display metadata.
Resolve through the explorer APItypescript
const name = 'ramestta.rama';
const response = await fetch(
  `https://latest-backendapi.ramascan.com/api/v1/1370/domains/${name}`
);
const domain = await response.json();

// Validate domain.address with your EVM address library before use.
console.log(domain);

Integration use cases

SurfaceHow to use RNS
WalletAccept a .rama name in the recipient field, resolve it, then show the destination address for confirmation.
Agent OSAssign a .rama name to the agent wallet so owners can distinguish agents from controller accounts.
MumbleChatUse the verified identity as an addressable messaging counterpart.
Dapp profileDisplay the primary or selected name alongside a verified wallet address.
Treasury toolingUse names for operator clarity, but keep multisig addresses as the authorization source.

Security requirements

  • Never authorize an action from a name string alone; authorize the resolved address and contract policy.
  • Re-resolve a name when initiating a sensitive transaction rather than relying on a stale local cache.
  • Clearly show when an address has changed since a user last used a name.
  • Treat text records as untrusted metadata unless your application validates their issuer and format.
⚠️Do not bypass confirmation
A name improves usability, not custody safety. High-value transfers should still display the destination address and follow the same owner or multisig approvals as direct-address transfers.

Found an issue with this page? Report on GitHub