Topic: Create and manage unlimited BTC addresses for users? (Read 208 times)
the idea of the bitcoin interface to manage various accounts in one interface is a good function in the platform that keeps users more confidence in the usage as it is an all-in-one platform for various reasons .
I don't get it 
What does it mean to generate addresses for users after all?
Users should generate address for themselves using a client side script or something, no need to scalability, no need to full node, 1 million user run a script on 1 million machines and your server will be informed of their wallet addresses and possibly an encrypted version of their private keys, etc. Am I missing something?
What does it mean to generate addresses for users after all?
Users should generate address for themselves using a client side script or something, no need to scalability, no need to full node, 1 million user run a script on 1 million machines and your server will be informed of their wallet addresses and possibly an encrypted version of their private keys, etc. Am I missing something?
He wants to have one public address for each client.
So when you buy something in his store, you will receive one unique address to deposit your bitcoin, to pay for the product you want.
If you share this address with multiple users it will be harder to control payments.
No need fixed address per customer. Just create multi bitcoin address, get notification all that address
But isn't it better to have a per-order address generation? Using a fixed address per customer is not the good practice, one should beware of security consequences.
This system will be able to do it per order.
I agree, it's better for privacy.
I don't get it
What does it mean to generate addresses for users after all?
Users should generate address for themselves using a client side script or something, no need to scalability, no need to full node, 1 million user run a script on 1 million machines and your server will be informed of their wallet addresses and possibly an encrypted version of their private keys, etc. Am I missing something?
What does it mean to generate addresses for users after all?
Users should generate address for themselves using a client side script or something, no need to scalability, no need to full node, 1 million user run a script on 1 million machines and your server will be informed of their wallet addresses and possibly an encrypted version of their private keys, etc. Am I missing something?
He wants to have one public address for each client.
So when you buy something in his store, you will receive one unique address to deposit your bitcoin, to pay for the product you want.
If you share this address with multiple users it will be harder to control payments.
You don't need full node to generate Bitcoin address and there are plenty script on GitHub to do that.
About scalable, i guess you should find/create script which support multi-threading and written on lower (not low) level programming language such as C++.
et that bitpay is hostile towards Bitcoin
About scalable, i guess you should find/create script which support multi-threading and written on lower (not low) level programming language such as C++.
et that bitpay is hostile towards Bitcoin
That's right, I need to create a bitcoin address for each user so they can deposit. Get notified about new deposit with addresses to be able to credit their accounts and then transfer Bitcoin from these addresses to our address. Do you have any recommends GitHub link?
I only can recommend https://github.com/nym-zone/segvan which made by nullius, a popular member in this forum. It has basic multi-core usage and it generates SegWit address which uses lower fees.
Thanks
I don't get it
What does it mean to generate addresses for users after all?
Users should generate address for themselves using a client side script or something, no need to scalability, no need to full node, 1 million user run a script on 1 million machines and your server will be informed of their wallet addresses and possibly an encrypted version of their private keys, etc. Am I missing something?
What does it mean to generate addresses for users after all?
Users should generate address for themselves using a client side script or something, no need to scalability, no need to full node, 1 million user run a script on 1 million machines and your server will be informed of their wallet addresses and possibly an encrypted version of their private keys, etc. Am I missing something?
He wants to have one public address for each client.
So when you buy something in his store, you will receive one unique address to deposit your bitcoin, to pay for the product you want.
If you share this address with multiple users it will be harder to control payments.
You don't need full node to generate Bitcoin address and there are plenty script on GitHub to do that.
About scalable, i guess you should find/create script which support multi-threading and written on lower (not low) level programming language such as C++.
et that bitpay is hostile towards Bitcoin
About scalable, i guess you should find/create script which support multi-threading and written on lower (not low) level programming language such as C++.
et that bitpay is hostile towards Bitcoin
That's right, I need to create a bitcoin address for each user so they can deposit. Get notified about new deposit with addresses to be able to credit their accounts and then transfer Bitcoin from these addresses to our address. Do you have any recommends GitHub link?
I don't get it
What does it mean to generate addresses for users after all?
Users should generate address for themselves using a client side script or something, no need to scalability, no need to full node, 1 million user run a script on 1 million machines and your server will be informed of their wallet addresses and possibly an encrypted version of their private keys, etc. Am I missing something?
What does it mean to generate addresses for users after all?
Users should generate address for themselves using a client side script or something, no need to scalability, no need to full node, 1 million user run a script on 1 million machines and your server will be informed of their wallet addresses and possibly an encrypted version of their private keys, etc. Am I missing something?
I believe bitpay.com is the way to go. Easy and tested a lot already.
1 million is not as a great number as it looks like.
Any bip39 seed can generate billions of addresses.
I believe that an xpub file can be transferred to the server and generate billions of public addresses without exposing any private keys.
1 million is not as a great number as it looks like.
Any bip39 seed can generate billions of addresses.
I believe that an xpub file can be transferred to the server and generate billions of public addresses without exposing any private keys.
I'm looking for a way to create and manage 1 million bitcoin addresses for 1 million of our users, any method is limitless and scalable. Open source methods and no full node load are preferred. Also there are any APIs that are not limited.
Any advise or guidance would be greatly appreciated..!!
Creating 1 million addresses should be simple/straight forward as long as you use a truly random input for generating private keys. But what do you mean by "manage".Any advise or guidance would be greatly appreciated..!!
Also note: when you yourself generate the addresses you also own the private key, this is not a preferred solution!
Yes, create BTC address for user deposit, receive notifications when there is a transaction to any address in it, then we can transfer the balance in all the addresses to other address.
I'm looking for a way to create and manage 1 million bitcoin addresses for 1 million of our users, any method is limitless and scalable. Open source methods and no full node load are preferred. Also there are any APIs that are not limited.
Any advise or guidance would be greatly appreciated..!!
Creating 1 million addresses should be simple/straight forward as long as you use a truly random input for generating private keys. But what do you mean by "manage".Any advise or guidance would be greatly appreciated..!!
Also note: when you yourself generate the addresses you also own the private key, this is not a preferred solution!
I'm looking for a way to create and manage 1 million bitcoin addresses for 1 million of our users, any method is limitless and scalable. Open source methods and no full node load are preferred. Also there are any APIs that are not limited.
Any advise or guidance would be greatly appreciated..!!
Any advise or guidance would be greatly appreciated..!!
Jump to: