<p><strong>Regarding number 1.</strong></p>
<p>Single Address Wallets aside from Nami and Lace, which you mentioned, are <a href="https://eternl.io/" rel="nofollow noreferrer">Eternl</a> which have single address mode, and <a href="https://typhonwallet.io/#/" rel="nofollow noreferrer">Typhon</a> which allows you to convert the wallet to a single address. These two have my personal recommendation.</p>
<p>At the end of <a href="https://docs.cardano.org/new-to-cardano/types-of-wallets" rel="nofollow noreferrer">this page</a>, you'll see a list of &quot;other wallets&quot; which has quite a few.</p>
<p><strong>Regarding number 2.</strong></p>
<p>There are many options to accomplish this. Something like <a href="https://cardanopress.io/" rel="nofollow noreferrer">CardanoPress</a> or <a href="https://github.com/osc707/cardano-connect" rel="nofollow noreferrer">Cardano Connect</a> do this for you. But if you are building your own tool, you can &quot;getUsedAddresses&quot; from the <a href="https://github.com/cardano-foundation/CIPs/tree/master/CIP-0030#apigetusedaddressespaginate-paginate--undefined-promiseaddress" rel="nofollow noreferrer">cardano wallet dapp bridge here</a>.</p>

CC BY-SA 4.0
2023-04-24T16:38:52.987Z
2023-04-24T16:38:52.987Z
PREEB
<p>Regarding the topic of single and multi-address wallets:</p>
<ol>
<li>What are the most commonly used single and multi-address based Cardano wallets? Are there any other single-address based wallets besides Nami or Lace that are live or currently being developed?</li>
<li>What are some strategies to manage multi-address wallet users in a web app? In my database I want to tie each user to their data by their wallet address, and for single-address based wallets there is no issue, however from my understanding some wallets like Yoroi and Eternl create a seemingly endless amount of wallet addresses because apparently in Cardano land you can make as many addresses derived from your private key as you want</li>
</ol>

<nami-wallet><cardano-address><webapp><eternl><lace-wallet>
Handling multi-address wallets in web apps
# Handling multi-address wallets in web apps

(Asked by: username_0 on 2023-04-24)

Regarding the topic of single and multi-address wallets:

1. What are the most commonly used single and multi-address based Cardano wallets? Are there any other single-address based wallets besides Nami or Lace that are live or currently being developed?
2. What are some strategies to manage multi-address wallet users in a web app? In my database I want to tie each user to their data by their wallet address, and for single-address based wallets there is no issue, however from my understanding some wallets like Yoroi and Eternl create a seemingly endless amount of wallet addresses because apparently in Cardano land you can make as many addresses derived from your private key as you want

**Tags:** nami-wallet, cardano-address, webapp, eternl, lace-wallet

---

## 1 answers

### Answer by username_1 on 2023-04-24. Score: 1 | Accepted answer

**Regarding number 1.**

Single Address Wallets aside from Nami and Lace, which you mentioned, are [Eternl](https://eternl.io/) which have single address mode, and [Typhon](https://typhonwallet.io/#/) which allows you to convert the wallet to a single address. These two have my personal recommendation.

At the end of [this page](https://docs.cardano.org/new-to-cardano/types-of-wallets), you'll see a list of "other wallets" which has quite a few.

**Regarding number 2.**

There are many options to accomplish this. Something like [CardanoPress](https://cardanopress.io/) or [Cardano Connect](https://github.com/osc707/cardano-connect) do this for you. But if you are building your own tool, you can "getUsedAddresses" from the [cardano wallet dapp bridge here](https://github.com/cardano-foundation/CIPs/tree/master/CIP-0030#apigetusedaddressespaginate-paginate--undefined-promiseaddress).


---

