From: "Luke-Jr" <luke@dashjr•org>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] [RFC] listtransactions reformatting
Date: Sat, 16 Jul 2011 13:14:11 -0400 [thread overview]
Message-ID: <201107161314.13267.luke@dashjr.org> (raw)
Example patch: http://tinyurl.com/6679go5
Changes:
* Additions to your wallet always are category:"receive", no matter what kind
of transaction
* Generated coins have an extra key, from:"generation"
* All transactions have a new key, status:
* "orphan" -- Another block chain invalidated this transaction (only for
generation?)
* "validating" -- Default stage for transactions; 0-2 confirmations for
ordinary sends, and 0-100 for generated coins
* "processing" -- 3-6 confirms for ordinary sends; 101-120 for generated
* "confirmed" -- over 6/120 confirmations
* "expired" -- for ordinary sends that have timed out without getting into a
block, or had its inputs otherwise respent
This change is proposed to fix webservices being ignorant of generated
transactions by keeping a standard category/format for all similar types of
entries.
Thoughts?
next reply other threads:[~2011-07-16 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 17:14 Luke-Jr [this message]
2011-07-16 19:59 ` Stéphane Gimenez
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=201107161314.13267.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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