Flagging accounts as (potentially) deprecated #5912

issue benjiqq opened this issue on March 16, 2015
  1. benjiqq commented at 9:33 PM on March 16, 2015: none

    I suggest taking some steps towards deprecating accounts.

    It's quite an important fact that use of accounts leads to potentially bad results.

    The following calls would be flagged for future deprecation.

    * getaccount Returns the account associated with the given address.
    * move [minconf=1] [comment] Move from one account in your wallet to another
    * setaccount Sets the account associated with the given address. Assigning address that is already assigned to the same account
    * listreceivedbyaccount [minconf=1] [includeempty=false] Returns an array of objects containing:
    * listaccounts [minconf=1] Returns Object that has account names as keys, account balances as values.
    * getreceivedbyaccount [account] [minconf=1] Returns the total amount received by addresses with [account] in transactions with at least [minconf] confirmations. If [account] not provided return will include all transactions to all accounts. (version 0.3.24)
    * getaccountaddress Returns the current bitcoin address for receiving payments to this account. If does not exist, it will be created along with an associated new address that will be returned.
    * getaddressesbyaccount Returns the list of addresses for the given account.
    
  2. luke-jr commented at 9:45 PM on March 16, 2015: member

    These are already deprecated in master (to be 0.11)

  3. laanwj commented at 6:45 AM on March 18, 2015: member

    This is in fact already done, see #5575

  4. laanwj closed this on Mar 18, 2015

  5. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-29 03:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me