Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hierarchical Deterministic BIP32 / BIP44 (HD) wallet #80

Open
taghvaei opened this issue Dec 26, 2017 · 6 comments
Open

Hierarchical Deterministic BIP32 / BIP44 (HD) wallet #80

taghvaei opened this issue Dec 26, 2017 · 6 comments

Comments

@taghvaei
Copy link

May I know if you supporting Hierarchical Deterministic BIP32 / BIP44 (HD) wallet so we can generate multiple child wallet which can connect to our main deposit wallet in BTCmarkets, if so can I have API documentation for it.

@justin-ngin
Copy link
Contributor

Hi @taghvaei ,

Could you please describe in a little more detail how you'd like BTC Markets to support HD wallets?

Thanks,
Justin

@taghvaei
Copy link
Author

In the ideal scenario while BTCmarket still keep private keys, I would like to manage my wallet creation process and structure in a way which their API let me to generate different child and parent public key as per my preference and order, but if it’s hard to implement this I would suggest to let us to generate a new unused deposit address for each currency ,

@justin-ngin
Copy link
Contributor

@taghvaei ,

Let me bring this up with the engineering team and see what they think. Could you shed some light on the use-case for this? I can see the benefits of having your own HD wallet and sets of keys, but I'm afraid I'm missing the benefit of child wallets stored in our platform. Please get back to me, and I'll update this issue moving forward with information regarding a possible implementation of this.

Thanks,
Justin

@taghvaei
Copy link
Author

taghvaei commented Jan 23, 2018

Thanks @justin-ngin ,
if you want to make a platform to receive fund from different user's or department of your company while you don't want to give one deposit public key to everyone and in the same time you want to keep track of transaction confirmation separately, currently many exchange provide this option for example Bitfinex deposit has a renew form which if it set to 1 and it will create a new address every time you call API.

https://bitfinex.readme.io/v1/reference#rest-auth-deposit

@taghvaei
Copy link
Author

taghvaei commented Feb 1, 2018

@justin-ngin any update?

@justin-ngin
Copy link
Contributor

@taghvaei ,

Sorry, no updates yet, but we haven't forgotten! I'll let you know as soon as I hear.

Cheers,
Justin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants