watch-address reports only new (unconfirmed) transactions

[ggutoski]

[Spawned from Issue 153]
watch-address seems to report only brand new (unconfirmed) transactions. New blocks are not reported, so each output always contains the line

block 0000000000000000000000000000000000000000000000000000000000000000

Seems redundant. It would be much nicer if there were a way to count transaction confirmations without resorting to polling. I mentioned this in Issue 13 and Eric's reply suggests that the intended behaviour for watch-address is to continue reporting with each new block in the blockchain.

[evoskuil]

It is not always the case that the transaction will be first discovered in the transaction pool, see the watch-address example.

It is true however that only transactions discovered subsequent to the subscription will be reported. The same link states:

This command reflects transactions created after the subscription is established.

This is by design, as otherwise the subscription would dump every transaction to a given address. However that is the intent of the fetch-history and fetch-balance commands. The design allows one to collect all (up to and including current tx memory pool) history if one desires, and to request notification of activity as it occurs.

I would categorize the remaining comments as a feature request, but I would recommend that a new issue be opened with a specific description of the scenario, since it's not entirely clear to me. It sounds like there's a desire to be notified every time a new block is mined, since that would be the case in which the confirmation level of a tx changes.