From: Gavin Andresen <gavinandresen@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] [RFC] listtransactions reformatting
Date: Sun, 17 Jul 2011 13:02:51 +1000 [thread overview]
Message-ID: <CABsx9T2qhLiYAQNOCigXOMySgVqDqqQMotqYQwSPZEwkSYbY=g@mail.gmail.com> (raw)
In-Reply-To: <201107161603.08960.luke@dashjr.org>
Fixing listtransactions (and listreceivedby/etc) so coin generation
transactions to particular addresses/accounts are credited to that
address/account is a good idea.
I don't think changing listtransactions output would be on the
priority list for any web services operators (in fact, I think most
would scream bloody murder if the output changed in a way that forced
them to change their code). The accounts-related things that I think
ARE on their high-priority list are:
1) Fixing getbalance and listtransactions performance problems when
you have hundreds of thousands of transactions and thousands of
accounts.
2) push-notification of coins received to accounts, so they don't have
to poll for changes.
--
--
Gavin Andresen
next prev parent reply other threads:[~2011-07-17 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 17:14 Luke-Jr
2011-07-16 19:59 ` Stéphane Gimenez
2011-07-16 20:03 ` Luke-Jr
2011-07-17 3:02 ` Gavin Andresen [this message]
2011-07-17 11:53 ` Amir Taaki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABsx9T2qhLiYAQNOCigXOMySgVqDqqQMotqYQwSPZEwkSYbY=g@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox