Bitcoin Global Name System · GNS Private Signet Demo

Prepare A Global Name System Transfer

Use this page to turn a known name state into a transfer-ready CLI handoff, then finish the on-chain transfer or sale flow with your signer.

GNS Private Signet Demo · Height - · 0 names · 0 pending

Transfer Flow

Start from a claimed name

Enter the name you want to move and the new owner pubkey you want to move it to.

Pick the right mode

The current state determines whether a simple gift handoff, an immature sale, or a mature sale fits best.

Finish in CLI and signer

The browser prepares the handoff. The CLI and your signer still build, sign, and broadcast the transfer transaction.

Back to explorer

How Transfers Work

The correct path depends on whether the name is still settling.

i

Immature names still depend on bond continuity. Mature names have a simpler ownership model, but sales can still be cooperative on-chain transactions.

Gift Or Pre-Arranged Transfer

  • Best when no seller payment needs to be embedded in the Bitcoin transaction.
  • For immature names, the current bond outpoint must be spent and a successor bond must be created.
  • The browser prepares a CLI handoff with the known state txids and bond details.

Buyer-Funded Immature Sale

  • Use this while the name is still immature and the buyer is funding the successor bond and seller payout in one transaction.
  • This is the safest on-chain sale path before maturity because bond continuity is preserved in the same transfer transaction.
  • The CLI command is submit-immature-sale-transfer.

Cooperative Mature Sale

  • Once the name is mature, the bond no longer determines validity.
  • The reference flow is a cooperative transaction that pays the seller and carries the Global Name System transfer event together.
  • The CLI command is submit-sale-transfer.

What The Browser Does

  • Looks up the current name state and tells you which transfer modes fit that state.
  • Pre-fills the known txids, bond amounts, and status-specific guidance.
  • Emits copyable CLI handoff blocks for the transfer path you choose.

Which Mode Should You Use?

Use the current name state to pick the cleanest transfer flow.

i

If the name is still immature, the successor bond matters. If the name is mature, sales and gifts are simpler to reason about.

Immature Name

  • Gift / pre-arranged: use submit-transfer and carry the bond forward to the new owner.
  • Sale: use submit-immature-sale-transfer so the buyer funds the successor bond and seller payout atomically.

Mature Name

  • Gift / pre-arranged: the current CLI can still use submit-transfer with the recorded bond details for a conservative handoff.
  • Sale: use submit-sale-transfer for the cooperative payment-plus-transfer transaction.

Prepare A Transfer

Choose the name and new owner, then build a state-aware handoff.

i

The browser looks up the current state and recommends the safest transfer mode. The actual transaction still gets built and signed outside the browser.

Enter a claimed name and the new owner pubkey to build a transfer-ready handoff.

Need To Inspect The Name First?

Use the explorer if you want to confirm the current state before building a transfer.

Return to explorer Open claim prep

Network Details

Resolver mode, chain source, and other lower-level debugging information for people who want it.

Technical info

Loading...

Loading...

-

-

Connecting to resolver

-