Bitcoin Forum
April 19, 2024, 10:27:57 PM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Create and manage unlimited BTC addresses for users?  (Read 185 times)
pocrypto (OP)
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
October 09, 2018, 10:41:32 AM
 #1

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..!!
"The nature of Bitcoin is such that once version 0.1 was released, the core design was set in stone for the rest of its lifetime." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
TheArchaeologist
Sr. Member
****
Offline Offline

Activity: 310
Merit: 727


---------> 1231006505


View Profile WWW
October 09, 2018, 10:56:15 AM
 #2

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".

Also note: when you yourself generate the addresses you also own the private key, this is not a preferred solution!

Sooner or later you're going to realize, just as I did, that there's a difference between knowing the path and walking the path
pocrypto (OP)
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
October 09, 2018, 11:02:30 AM
 #3

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".

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.
bitmover
Legendary
*
Offline Offline

Activity: 2282
Merit: 5878


bitcoindata.science


View Profile WWW
October 09, 2018, 11:34:53 AM
 #4

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.

.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
aliashraf
Legendary
*
Offline Offline

Activity: 1456
Merit: 1174

Always remember the cause!


View Profile WWW
October 09, 2018, 12:15:31 PM
 #5

I don't get it  Huh

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?
pocrypto (OP)
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
October 09, 2018, 12:42:22 PM
 #6

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

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?
bitmover
Legendary
*
Offline Offline

Activity: 2282
Merit: 5878


bitcoindata.science


View Profile WWW
October 09, 2018, 01:17:14 PM
 #7

I don't get it  Huh

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.

.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
pocrypto (OP)
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
October 09, 2018, 02:05:58 PM
 #8

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

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
aliashraf
Legendary
*
Offline Offline

Activity: 1456
Merit: 1174

Always remember the cause!


View Profile WWW
October 09, 2018, 02:19:07 PM
 #9

I don't get it  Huh

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.
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.
bitmover
Legendary
*
Offline Offline

Activity: 2282
Merit: 5878


bitcoindata.science


View Profile WWW
October 09, 2018, 02:36:25 PM
 #10

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.

.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
pocrypto (OP)
Newbie
*
Offline Offline

Activity: 41
Merit: 0


View Profile
October 09, 2018, 02:40:02 PM
 #11

I don't get it  Huh

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.
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.

No need fixed address per customer. Just create multi bitcoin address, get notification all that address
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!