|
Title: Merchant processing alternative Post by: mokimarket on November 21, 2011, 07:09:13 PM Instead of issueing a random address for payment with each transaction, couldnt you just assign a unique ID to each user to the end of each payment?
So if user #43 in your sytem wants to purchase something worth 1.542 bitcoins. Your system would request that they send 1.542000043 bitcoins, where the 000043 would be the unique identifier for that account; you could also generate a random sequence per each account. This is the system I am implementing on mokimarket, what do you guys think? Title: Re: Merchant processing alternative Post by: DeathAndTaxes on November 21, 2011, 07:16:23 PM You certainly could but why?
If user has a typo then they don't get credit for their funds? It is too easy to generate a unique address for each user. Title: Re: Merchant processing alternative Post by: mokimarket on November 21, 2011, 07:36:48 PM You certainly could but why? If user has a typo then they don't get credit for their funds? It is too easy to generate a unique address for each user. I see your point, I just figured it would be just as easy to copy/past unique address as it would be a unique payment. And user would still get credit, it would just take longer. Another advantage is that I can store my wallet offline; wouldn't I have to have my wallet.dat file on server if I wanted to generate unique addresses? Title: Re: Merchant processing alternative Post by: DeathAndTaxes on November 21, 2011, 07:45:29 PM Your wallet wouldn't need to be online (or at least not on the store server). You can pre-generate 100,000 addresses and only load the public address on the store webserver, giving each user a unique one from the list. When the list runs low you could upload another 100,000 addresses.
|