Skip to content

Sources behind this page

Every claim on this page resolves to these pinned revisions. Follow a path to read the exact source the statement was verified against.

atomicals-electrumx-1.5.2.0

Atomicals ElectrumX

Revision v1.5.2.0 (2025-03-27)

Open pinned path: realmValidation

Version-sensitive ARC-20 and Atomicals validation behavior used as the pinned reference baseline.

Paynames

Raw

Using a Realm as a payment destination, what resolution guarantees, and the checks a payer must run first.

Protocol behavior Verified 2026-08-31 Metadata & Sources

Describes the Atomicals protocol itself at the pinned reference revision. It does not promise that any product exposes it.

Page ID
protocol/realms/paynames
Normative authority
Atomicals reference implementation
Networks
mainnet
Documentation version
2026.08
Audience
everyone, developer
Owner
bitcoin-universe-docs
Sources
Known limitations
  • Resolution is computed at a chain position and by one implementation. A payer who resolves once and caches the answer can pay the wrong destination later.

import { Aside } from ‘@astrojs/starlight/components’

A Payname is a Realm used as a payment destination. Instead of a raw address, a payer uses a name that resolves to one.

That, at the height and generation the answer was computed, this name resolved to this Atomical, whose current location is this output, whose owner script is this.

That is a chain of four facts. Every one of them can change.

  1. Resolve the name to an Atomical ID.
  2. Read the Atomical’s current location and owner script.
  3. Confirm the resolution generation is current, not cached.
  4. Display the resolved address to the payer for confirmation.
  5. Check the name for confusable characters against names the payer has used before.
  6. For a significant amount, resolve through a second compatible source and compare.

Step four is not optional. A payer who never sees the address cannot detect a wrong resolution.

Two names can render identically and be different strings. A payer who copies a name from a message may be copying a lookalike.

See Unicode and IDNA for the normalisation rules and the warnings a product must show.

  • Never resolve once at page load and pay later from the cached answer.
  • Never hide the resolved address behind the name.
  • Never treat a name as proof of who the recipient is.
  • Never auto-fill a payment from a name found in untrusted content.