For a blockchain or wallet integration you need the basic public key (public wallet address) of your wallet. With wallet providers such as Ledger, Exodus and others, an extended public key (xpub, public account address) may be required for certain blockchains (BTC, BCH, DOGE, LTC, ADA).
At a glance
👁️ You find the public key in your wallet. It is the public address and not a secret. Blockpit uses it to read balances and transaction history. Basic public keys work for all blockchains, extended public keys only for certain ones, mainly with wallet providers such as Ledger, Exodus or BitBox (HD wallets). You find examples of both address types further down in this article.
You have … | You enter … |
a Bitcoin address (starts with 1, 3 or bc1) or an Ethereum address (starts with 0x) | the basic public key (wallet address) |
a Ledger, Exodus or BitBox wallet with BTC, BCH, DOGE, LTC or ADA | possibly the extended public key (account address, e.g. xpub, ypub, zpub) |
an xpub that does not work | the same key with the prefix ypub or zpub |
Adding an automatic blockchain/wallet integration
1️⃣ In the Dashboard, open the Integrations tab and click + Integration.
WebApp View
MobileApp View
2️⃣ Choose the right blockchain or wallet provider. (You can choose between Blockchain, Wallet, Exchange and Manual.)
3️⃣ Enter a name for your integration, plus a public wallet address (Legacy, Bech32, Segwit, ERC20) or a public account address (Ledger, Trezor, Exodus and others).
4️⃣ Let Blockpit check whether your address belongs to the EVM network (Ethereum Virtual Machine) and is therefore active on several blockchains: keep the advanced settings and confirm with Continue.
If your address is EVM-enabled, you select which active blockchains you want to import as a standalone wallet integration.
5️⃣ To finish, click Continue. Blockpit creates your wallet(s) and imports asset balances and transactions automatically.
💡 Tip: Keep First Transaction (Full History) as the default import period. A specific start date only makes sense if you want to add transactions from before that date manually.
💡 Tip: When you create multi-wallet integrations such as Trezor, Ledger and others, you can add more blockchains (wallets) step by step. Blockpit groups all wallets in one folder, and you can add existing or future integrations to it later.
What happens next, and how do I undo it?
The wallet appears as an integration in the Integrations tab, and balances and transactions are imported automatically. You delete a wrongly created integration as described in the management article (deleting is permanent):
Which key do I need, and what if something goes wrong?
If you use Ledger, Exodus or a similar wallet for BTC, BCH, DOGE, LTC or ADA, you may need the extended public key instead of the basic address.
If an xpub does not work, change the prefix to ypub or zpub and try again.
If your address is EVM-enabled, select the active blockchains you want to import as their own wallet integration.
Typical mistakes
✗ Entering only the basic address for Ledger or Exodus → for BTC, BCH, DOGE, LTC or ADA an extended public key may be required
✗ Giving up when the xpub does not work → change the prefix to ypub or zpub and try again
✗ Choosing a specific start date instead of First Transaction → transactions before the start date are missing and have to be added manually
When is the basic public key (public wallet address) used?
Basic public keys (public wallet addresses) are used by all blockchains:
Blockpit uses your public wallet address to read holdings (asset balance) and the related transaction history. It is often also called paper wallet or public key.
Example of a Bitcoin paper wallet address (starts with 1, 3 or bc1):
34MpgrLDLbBTp9XY12FZKMEj33Jvrk7djs
Example of an Ethereum wallet address (starts with 0x):
0x1b073382e63411e3bcffe90ac1b9a43fefa1ec6f
When is the extended public key (public account address) used?
Extended public keys (public account addresses) are only used by certain blockchains. In addition to public wallet addresses (public keys), there are public account addresses (extended public keys). Wallet providers such as Ledger, Exodus, BitBox or similar use them to combine several sub-wallets (public keys) in your account (HD wallets).
How do I add a Bitcoin integration with an extended account address [xpub]?
Example of an extended Bitcoin account address:
xpub6BosfCnifzxcFwrSzQiqu2DBVTshkCXacvNsWGYJVVhhawA7d4R5WSWGFNbi8Aw6ZRc1brxMyWMzG3DSSSSoekkudhUd9yLb6qx39T9nMdj (starts with xpub, ypub or zpub)
💡 Update: Automatic detection of the correct extended public keys
Blockpit now automatically detects the correct extended public key (x/y/zpub, etc.) when you add blockchain integrations for Bitcoin, Litecoin, Dogecoin, Bitcoin Cash and Dash.
How do I add a Bitcoin integration with an extended Taproot account address [tr(xpub)]?
Example of an extended Bitcoin Taproot account address:
tr(xpub6BosfCnifzxcFwrSzQiqu2DBVTshkCXacvNsWGYJVVhhawA7d4R5WSWGFNbi8Aw6ZRc1brxMyWMzG3DSSSSoekkudhUd9yLb6qx39T9nMdj)
If the integration does not work with xpub keys, you can change the prefix of the xpub key to ypub or zpub as shown above and try again.
Other blockchains with their own key abbreviation
Dogecoin (DOGE) works analogously with the abbreviation dgub instead of the xpub used for Bitcoin.
Litecoin (LTC) works analogously with the abbreviations Ltub, Mtub and zpub instead of the prefixes xpub, ypub and zpub used for Bitcoin.
Cardano (ADA) works analogously with the abbreviations acct_ (Daedalus), xpub (Shally Era) or 128+ character hex keys (Yoroi).