Greetings,
I'm looking for some advice regarding a service I'm working on.
One of my requirements leads me to need multiple addresses per user.
Additionally, due to how accessible I intend to make this service, it's trivial for any visitor to generate a dozen addresses before the system tells them they've reached a limit.
I however am able to make an address given to a user valid for only 48 hours. So in the event of abuse, addresses do get returned to a pool after 48 hours.
Basically, in the worst case I'll need a pool of addresses of at least 20-40 times the amount of peak daily visitors.
Of course, I can't predict the amount of daily visitors yet. But I would like to be able to scale up easily if needed.
That said, I'm looking for advice from people that have created or maintained a service with a large pool of addresses.
How many addresses did you comfortably use on a single wallet?
Were you required to scale beyond a single wallet?
Are there performance considerations I should be aware of?
Topic: Wallets with many addresses, what are practical limits? (Read 377 times)
Jump to: