public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Stéphane Gimenez" <dev@gim.name>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] listtransactions reformatting
Date: Sat, 16 Jul 2011 21:59:07 +0200	[thread overview]
Message-ID: <20110716195907.GA311029@tenebreuse> (raw)
In-Reply-To: <201107161314.13267.luke@dashjr.org>

Hi,

You may have a look at the following proposal. It associates
generations txouts with the appropriate addresses and accounts.
(See my previous mail)

https://github.com/sgimenez/bitcoin/commit/a8e6510042f2f7f951414c7da124668b30da4acd

> * Additions to your wallet always are category:"receive", no matter
>   what kind of transaction

Either this, or maybe webservices should be told to forget about
categories and to rely only on the sign of the amounts. Maybe a "type"
field with values "credit"/"debit" could help them? This way, more
categories could be added later (escrow transactions, or other scripts
that might be standardized).

An official API guide (not just a technical reference) would be very
valuable here.

Last, I agree that {list,get}receivedby* should include generated
amounts, because there is currently no way to do this for
generations. (This issue is not addressed by my patch yet)

Best,
Stéphane



  reply	other threads:[~2011-07-16 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 17:14 [Bitcoin-development] [RFC] listtransactions reformatting Luke-Jr
2011-07-16 19:59 ` Stéphane Gimenez [this message]
2011-07-16 20:03   ` Luke-Jr
2011-07-17  3:02     ` Gavin Andresen
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=20110716195907.GA311029@tenebreuse \
    --to=dev@gim.name \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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