# Gavin Andresen
# 2011-03-27 17:51:41
# https://bitcointalk.org/index.php?topic=5011.msg73553#msg73553

So...  I'm working on a patch to add @p{lt} COINBASE_MATURITY-confirmation generation transactions to standard listtransactions, and trying to figure out the right way to handle immature generation transactions. @p{par}

Either: @p{brk}
a) list them as 'generate' @p{--} they'll just happen to have confirmations @p{lt} 100 (100 is the COINBASE_MATURITY, although the GUI doesn't show them until confirmations@s{gt}= 120). @p{par}

b) list them as 'immature' @p{--} a new transaction category. @p{par}

I'm leaning towards (b), because that way apps don't have to know that COINBASE_MATURITY is 100, and it is easier to double-check that listtransactions agrees with the getbalance API calls (immature coins are never counted in balances, because they can't be spent until they mature). @p{par}

The only drawback I can think of is that adding a new transaction category might confuse existing code. @p{brk}