Thousands of addresses on one accouny is the correct way to do it. Many accounts per wallet is bad.

Sent from my SCH-I535 using Tapatalk

Excellent - many thanks :)

Quote from: monsterer on January 23, 2015, 09:00:06 AM

Quote from: xeroc on January 18, 2015, 02:01:30 PM
... afaik those addresses can be regenerated ..

Many thanks - do you know if this will scale to thousands of addresses on a single account ok?

From what I remember of some posts of @toast, some exchanges (read: bter.com) having just a single account name and generating a new address for every single deposit .. still manage to run the client .. toast once told us that the filesizes of their backups are in the gigabytes   :o

Quote from: xeroc on January 18, 2015, 02:01:30 PM
... afaik those addresses can be regenerated ..

Many thanks - do you know if this will scale to thousands of addresses on a single account ok?

... afaik those addresses can be regenerated ..

help wallet_address_create

A common merchant workflow is to generate a new bitcoin address for every site user, so you can map deposited funds to user.

With bitshares the closest thing you can do is to generate a new private key and then call wallet_import_private_key and hand out the bitshares address to the user.

Is this a feasible workflow, will it scale ok?