I want to have multiple “accounts” with unique balances and to send and receive coins on a per-account basis. The equiv. of having multiple wallets running at the same time.
It would help to simply list the balance for each ‘receiving address’ and to specify a ‘source’ address when sending coins.
I have the beginning of something like this. It’s mostly like what Gavin described.
Some more rpc interface:
move <fromaccount> <toaccount> <amount>
Move from one internal account to another. I think blank account name (“”) will be your default account. If you sell something to a user, you could do move “theiraccount” “” 123.45.
Is “move” the best name for this? I shied away from “transfer” because that sounds too close to sending a transaction.
I’m thinking a new function getaccountaddress instead of overloading getnewaddress:
Gives you an address allocated from getnewaddress <account>. It’ll keep giving the same address until something is received on the address, then it allocates a new address. (It automatically does what the sample code I posted some time ago did)
Would these commands make it possible in simple cases to implement your website without needing a database of your own?
85,632 total views, 89 views todayhttps://bitcointalk.org/index.php?topic=665.msg18349#msg18349