<p>I don't see any problems in doing it this way. Just make sure you save the recovery words in safe places, to be able to recover the wallet.
You can also take a look at my script here to see the way I'm using to manage some of my wallets:
<a href="https://gist.github.com/cardano-apexpool/99784308812bdf7aa01446fa95f47fd2" rel="nofollow noreferrer">https://gist.github.com/cardano-apexpool/99784308812bdf7aa01446fa95f47fd2</a></p>

CC BY-SA 4.0
2022-07-10T06:41:32.750Z
Thank you for taking a look at my question and responding!
Thanks too for the link to your repo.  
- @data_relevant
RelevantData
CC BY-SA 4.0
2022-07-10T06:29:32.367Z
2022-07-10T06:29:32.367Z
George - APEX Stake Pool
<p>Does it matter when a receiving address is used to receive ADA into a wallet?
For example:</p>
<ul>
<li>I use cardano-node/cardano-wallet to create a wallet.</li>
<li>I then generate 100 receiving addresses for that wallet.</li>
<li>I store the receiving addresses in a database table</li>
<li>Over time, as needed, I use one of the receiving addresses to allow a user of a service to send ADA to the wallet, I mark that address as &quot;Used=1&quot; in the table, and use the next unused address the next time one is needed for that same customer, or a different customer.</li>
<li>At some point, if unused addresses are getting low, I get a notification - and proceed to generate more receiving addresses and add them to the table to replenish the pool of unused addresses.</li>
</ul>
<p>There are some benefits to doing this in this way...do you see problems with this methodology? Is it not feasible because of a time-based limitation on using a receiving address generated for a wallet or some other such issue I am not aware of?</p>
<p>Does this seem like a reasonable strategy at least until I have a more dynamic/on-demand wallet address generating system devised/implemented?</p>
<p>Thank you!</p>

<wallet><cardano-node>
Pre-creating Cardano Wallet Receiving Addresses for later use
# Pre-creating Cardano Wallet Receiving Addresses for later use

(Asked by: username_0 on 2022-07-10)

Does it matter when a receiving address is used to receive ADA into a wallet?
For example:

* I use cardano-node/cardano-wallet to create a wallet.
* I then generate 100 receiving addresses for that wallet.
* I store the receiving addresses in a database table
* Over time, as needed, I use one of the receiving addresses to allow a user of a service to send ADA to the wallet, I mark that address as "Used=1" in the table, and use the next unused address the next time one is needed for that same customer, or a different customer.
* At some point, if unused addresses are getting low, I get a notification - and proceed to generate more receiving addresses and add them to the table to replenish the pool of unused addresses.

There are some benefits to doing this in this way...do you see problems with this methodology? Is it not feasible because of a time-based limitation on using a receiving address generated for a wallet or some other such issue I am not aware of?

Does this seem like a reasonable strategy at least until I have a more dynamic/on-demand wallet address generating system devised/implemented?

Thank you!

**Tags:** wallet, cardano-node

---

## 1 answers

### Answer by username_1 on 2022-07-10. Score: 2 | Accepted answer

I don't see any problems in doing it this way. Just make sure you save the recovery words in safe places, to be able to recover the wallet.
You can also take a look at my script here to see the way I'm using to manage some of my wallets:
<https://gist.github.com/cardano-apexpool/99784308812bdf7aa01446fa95f47fd2>

> **Comments:**
> **username_0**: Thank you for taking a look at my question and responding! Thanks too for the link to your repo.   - @data_relevant  

---

