Skip to main content
Bitcoin Best Practices: Interacting With dApps

Understanding how Bitcoin wallets connect to dApps.

Updated over 4 months ago

When using Bitcoin dApps like Magic Eden, only Native Segwit & Taproot addresses are recognized. Legacy and Nested Segwit addresses are NOT supported.

Connecting to Magic Eden

If you are using a wallet provider that generates 2 wallet addresses like the Magic Eden Wallet (one for Payment, one for Ordinals), the Taproot address will be address that's connected. Please note that you should not send any spendable Bitcoin to this address as it is Taproot. More information on this can be found in this article.

Any inscriptions, Rare Sats or Runes purchased will be sent to the taproot address. You will also only be able to list the inscriptions that are stored on your Taproot address.

The Native Segwit address is only used to facilitate payments.

If you have any inscriptions on your Native Segwit address, you'd need to get them isolated and extracted to your Taproot address. Learn more here.

Wallet Types Accepted on Magic Eden at a Glance

Wallet providers use various address types, thus different address types will be used for Payment & Ordinals when connecting to Magic Eden. Here's a breakdown:

Wallet Provider

Payment

Ordinals

Magic Eden Wallet

Native Segwit [bc1q]

Taproot [bc1p]

Xverse Wallet

Nested Segwit [3]

Taproot [bc1p]

Unisat Wallet*

Native Segwit [bc1q] or
Nested Segwit [3] or
Taproot [bc1p]

Native Segwit [bc1q] or
Taproot [bc1p]

* Unisat Wallet gives users the flexibility to select the type of address they wish to generate upon creating/restoring their wallet. However, it only utilizes that selected address type for Payments & Ordinals, so the same address will be used when connecting to dApps.

Did this answer your question?