Author Topic: Feasible? using wallet_import_private_key to replicate bitcoin's getnewaddress?  (Read 1717 times)

0 Members and 1 Guest are viewing this topic.

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
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

Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline monsterer

My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
... 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

Offline monsterer

... afaik those addresses can be regenerated ..

Many thanks - do you know if this will scale to thousands of addresses on a single account ok?
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline monsterer

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?
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads