# Gavin Andresen
# 2011-03-27 19:21:04
# https://bitcointalk.org/index.php?topic=5011.msg73591#msg73591

Pull request: @s{(link)} @p{par}

From a testnet-in-a-box test, here's what mature/immature blocks look like: @p{brk}

Code:
    { @p{brk}
        "account" : "", @p{brk}
        "category" : "generate", @p{brk}
        "amount" : 50.00000000, @p{brk}
        "confirmations" : 120, @p{brk}
        "txid" : "14da5ea78b6a1451ba11445be08c520808ddd185cf55d550f012dd4c16e2f67d", @p{brk}
        "time" : 1300074965 @p{brk}
    }, @p{brk}
    { @p{brk}
        "account" : "", @p{brk}
        "category" : "immature", @p{brk}
        "amount" : 50.00000000, @p{brk}
        "confirmations" : 119, @p{brk}
        "txid" : "8181f1760c208c84f06183f1145d3ad5a142340fd331e63466d5de8c406435aa", @p{brk}
        "time" : 1300075032 @p{brk}
    }, @p{brk}

 @p{brk}
PS:  There is a feature in the core bitcoin code that bothers me because I don't completely understand it:  coinbase transactions are technically spend-able after 100 confirmations (COINBASE_MATURITY in the code), but they aren't counted as spendable by the GUI or the RPC until 120+ confirmations (GetBlocksToMaturity() in the code).  I suppose a big block-chain re-org could run into problems if a just-barely-mature generation was spent at exactly the wrong time, but I need to think about that a bit more (and maybe ping satoshi...). @p{brk}