Skip to content
Universe Wallet

Payment and asset addresses

One recovery phrase produces several Bitcoin addresses, in different formats, all yours at the same time. People call one of them the payment address and another the asset address. That shorthand is useful, and it is also not how Bitcoin works. Both halves of that matter.

One recovery phrase, four address lanes, and what each lane is forA single twelve word recovery phrase sits at the top. Below it, key derivation produces four Bitcoin address lanes from the same phrase. Native SegWit at derivation path m slash 84, addresses beginning bc1q, is the default payment lane. Nested SegWit at m slash 49, addresses beginning 3, exists for older services that cannot pay a bech32 address. Taproot at m slash 86, addresses beginning bc1p, is the lane where inscriptions and most protocol assets are conventionally held. Legacy at m slash 44, addresses beginning 1, is the oldest format and costs the most to spend. A closing note states that no address type is an asset address at the protocol level: an artifact lives on a specific output, and moving that output is what moves the artifact.ONE PHRASE, FOUR LANESSecret Recovery Phrase (12 words)Every address below is derived from these words. Nothing else is needed to recreate them.Native SegWitm/84'/0'/0'bc1q...Default lane. Plain payments in and out. Cheapest to spend.PAYMENT LANETaprootm/86'/0'/0'bc1p...Where inscriptions and most protocol assets are held by convention.ARTIFACT LANENested SegWitm/49'/0'/0'3...Compatibility lane, for a service that cannot pay a bc1 address.Legacym/44'/0'/0'1...Oldest format. Largest transactions, so the highest fee to spend.THE PART PEOPLE GET WRONGBitcoin has no "asset address". An inscription or a token balance lives on one specific output,not on an address. Spending that output is what moves the artifact, whatever lane it sits in.

All four lanes come from the same words. Universe Wallet defaults to Native SegWit for payments and shows Taproot as the lane where inscriptions and most protocol assets are conventionally held. The distinction is a convention among wallets and marketplaces, not a rule the network enforces.

What is actually true

Section titled “What is actually true”

An inscription, a rune balance, or a token balance is attached to a specific unspent output, not to an address. The address is just the lock on that output.

That has three consequences worth internalising:

  1. Any address type can hold an artifact. Nothing stops an inscription from sitting on a Native SegWit output. Marketplaces and indexers conventionally expect Taproot, so a non-standard placement can be harder to trade, but it is not invalid.
  2. Spending the output moves the artifact. If a payment happens to select the coin an inscription sits on, the inscription goes wherever that coin goes. This is the accident Universe Wallet exists to prevent, and it is covered in Protected outputs.
  3. You cannot make an address safe. There is no address setting that protects an artifact. The protection lives in coin selection, not in the address.

Why the shorthand still helps

Section titled “Why the shorthand still helps”

Keeping artifacts on one address type and everyday money on another has a practical benefit: it reduces the number of coins that a routine payment could reach in the first place. It is a tidiness habit, not a security boundary.

If you use one address for everything, Universe Wallet still classifies every coin before selecting it. The habit helps; the classification is what actually protects you.

Which address to give out

Section titled “Which address to give out”
SituationGive them
Someone is paying you in bitcoinYour default receiving address. Native SegWit unless you changed it.
A marketplace is sending you an inscription or an ordinalYour Taproot address, unless the marketplace asks for something specific.
A service says it cannot pay a bc1 addressYour Nested SegWit address, which starts with 3.
A service only accepts addresses starting with 1Your Legacy address. Expect to pay more to spend it later.
Section titled “Related”