bitcoin/bitcoin — pull request #1409 by luke-jr (2012-06-02 02:52:47+00:00)
Title: Treat generation (mined) transactions less different from receive transactions

- Show address receiving the generation, and include it in the correct "account"
- Multiple entries in listtransactions output if the coinbase has multiple outputs to us
- Classify generation as "receive" category, so it doesn't require special treatment for payment services
- Add new "status" key to wallet transactions, which is:
- - "confirmed" -- 6+ confirmations (120+ for generation)
- - "processing" -- 2+ confirmations (100+ for generation)
- - "validating" -- 0+ confirmations ( 1+ for generation)
- - "invalid" -- negative confirmations (contradicted in main chain)

Goal: don't make service providers have to jump through near-impossible hoops to handle receiving generated payments/deposits (right now, only MtGox actually handles them correctly); this also makes things nicer for miners who receive to their own wallets (eg, they can tell which pool it came from)