# Gavin Andresen
# 2010-12-01 13:29:53
# https://bitcointalk.org/index.php?topic=2025.msg25876#msg25876

@s{quotedtext}
@s{quotedtext}
 @p{brk}
You can continue to use accounts as labels, create an each-address-gets-one-label, and map addresses@p{--}@s{gt}user in your database. @p{par}

However, your application will be faster and simpler if you let bitcoin do the addresses@p{--}@s{gt}user mapping (one account per user), and store address@p{--}@s{gt}user-specified-label in your database. @p{par}

The bitcoin 'getaddressesbyaccount' method will give you the addresses@p{--}@s{gt}user relationship, and all the accounting becomes much easier (listtransactions gets you all the transactions associated with a particular user, etc). @p{par}


@s{quotedtext}
@s{quotedtext}
 @p{brk}
The label methods still work, call the corresponding account methods (e.g. call setlabel @p{lt}bitcoinaddress@s{gt} and it calls setaccount), but are deprecated, so they don't show up in the help and will eventually be removed. @p{par}

The only 'potentially breaking change' is the sendtoaddress function, which now returns a transaction id instead of the word 'sent'. @p{brk}