Author

Topic: Bitcoind RPC-API confusion about "Address" labeling (Read 415 times)

newbie
Activity: 137
Merit: 0
Update

I've recovered my wallet.dat to get rid of test-accounts that are unable to removed/renamed. If there is really no suiteable API to do that one is much more flexible by having database/mysql assignment of wallet-addresses to customers than doing that by such an unflexible Bitcoin API.

If there is a better solution please let me know ;-)
newbie
Activity: 137
Merit: 0
Hello,

I've just came up to do some testing on how to start using the Bitcoind RPC API. I've done some testing and created some Accounts with BTC-Addresses associated.

I've created f.e. Accounts called "Test". In my understanding this Accounts are used to f.e. group Addresses to one customer or a a set of transactions (f.e. one customer or a set of transactions).

If f.e. a customer dropped his account it may be useful to be able to move the transactions on those adresses to another account and drop the "left empty" account.

I initally thought that setaccount (previously named setlabel in the API) would do right that. But after trying and reading I figured out that this only moves the amount of transactions from one account to another.

The "empty" container (Account) is left as it is. So to bring it on the point... we're going to start garbage collection here which will lead into massive confusion of accounts left that we don't need...?

Is there any way to delete or rename an account or completly move it physically to another one like "merging" (by getting rid of the old one)?


Best regards
Gabriel
Jump to: