Bitcoin Global Name System · GNS Private Signet Demo

Prepare A Global Name System Claim

Use this page to build the claim package, commit payload, and reveal payload, then finish the PSBT and signing flow in Sparrow or another external signer.

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

Claim Flow

Pick a name

Start from a name you already looked up, or type one directly into the claim tool.

Prepare the package

Generate the commit and reveal inputs here so your wallet builder has the exact protocol bytes.

Finish in your signer

Build and sign the PSBTs in Sparrow or another external signer, then come back and watch the lifecycle.

Back to explorer

How To Claim

Plan the claim here, then finish the commit and reveal in your signer.

i

The website prepares the protocol-specific bytes. Your signer still controls the transaction signatures and broadcast.

What The Website Does

  • Builds the claim draft data you need for a signer flow.
  • Shows the exact commit and reveal payloads required by the protocol.
  • Can generate Sparrow-native commit and reveal PSBTs when you provide wallet metadata.
  • Lets you export a claim package for a CLI or wallet-assisted workflow.
  • Lets you come back and watch the lifecycle after broadcast.

What You Do Next

  1. Choose an available name and prepare the claim package here.
  2. Build and sign the commit and reveal PSBTs in Sparrow or another external signer.
  3. Broadcast the commit, wait for confirmation, then reveal within 6 blocks.
  4. Return to the explorer to watch the name move from pending to immature and later mature.

Get Demo Coins First

Fund a Sparrow signet wallet for this private demo.

i

This deployment runs on our own private signet, so public signet faucets are not involved.

  • Paste a receive address from Sparrow.
  • The site sends demo coins and mines a confirming block.
  • Use the same wallet to build the claim transaction.

What To Do In Sparrow

  1. Open a signet wallet in Sparrow.
  2. Copy a fresh receive address from that wallet.
  3. Paste it below and request demo coins.
  4. Wait for the wallet to refresh, then continue with claim prep on this page.

What You Will Receive

  • 1,000,000 sats (0.01 BTC) per request.
  • One block is mined immediately after funding, so the coins land confirmed.
  • This is usually enough for an 8+ character demo claim plus fees.
  • If you want a shorter name, request another top-up after the cooldown.

Need Sparrow First?

  • Download Sparrow Wallet from the official site.
  • Start it in signet mode, then connect it to this private demo node.
  • If you are running locally from the repo, the included Sparrow helper scripts can configure the connection for you.
Paste a Sparrow receive address above to get demo coins on this private signet network.

Sparrow-Friendly Signer Workflow

Use this when you want the manual signing flow spelled out.

i

Global Name System can generate wallet-aware PSBTs for the private demo, but the signing responsibilities still stay in Sparrow.

Bring These Into Sparrow

  • The desired name, owner pubkey, and nonce.
  • A destination for the bond output and, optionally, a change destination.
  • The exact commit payload bytes from this page.
  • The required bond amount and the bond vout you want to preserve.

Commit In Sparrow

  1. Create a transaction with a dedicated bond output holding at least the required bond.
  2. Add the commit OP_RETURN output using the payload shown here.
  3. Sign and broadcast the commit transaction.
  4. Copy the final commit txid back into this page so the reveal payload can be derived.

Reveal After Confirmation

  1. Wait for the commit to confirm.
  2. Use the derived reveal payload and reveal transaction skeleton from this page.
  3. Sign and broadcast the reveal within the 6-block reveal window.
  4. Return to the explorer to watch the name move from pending to immature.

Common Pitfalls

  • Do not let fees shrink the bond output below the required bond amount.
  • Keep the bond at the vout declared in the claim draft.
  • Do not wait too long after commit confirmation or the reveal window will expire.
  • The browser is not signing for you, so every broadcastable transaction still needs to come from your signer.

Prepare A Claim

Build the draft and exports you need for your signer.

i

This tool handles the name-specific claim package, commit payload, and reveal payload.

  • Bond Destination is where the claim bond output should land.
  • Owner Pubkey controls later name-level actions like values and transfers.
  • Commit Txid stays empty until after commit broadcast, then lets the page derive the reveal payload.
No generated test key yet. Use Generate Test Key for local prototype work only.
Enter a name and owner pubkey to generate the claim draft inputs.

Build Sparrow PSBTs

Paste the account metadata from Sparrow and the site will generate ready-to-sign commit and reveal PSBTs for this private signet demo. For higher-value bonds, use the offline architect instead.

Prepare a claim draft, then paste Sparrow wallet metadata to generate ready-to-sign PSBTs.

Hosted Convenience, Sovereign Option

Use the hosted claim page for speed, then switch to the offline architect whenever the bond amount justifies the extra caution.

i

The hosted site is the convenience layer. The offline architect is the sovereignty layer.

  • Hosted flow: fastest path for everyday demos and low-risk testing.
  • Offline architect: download a single-file claim builder and run it locally with pasted UTXOs and wallet metadata.
Download Sparrow Open offline architect Download offline architect Return to explorer

Network Details

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

Technical info

Loading...

Loading...

-

-

Connecting to resolver

-