Olaoluwa Osuntokun b913bda472 chainntfs: expand ChainNotifier interface ... * The `NotificationTrigger` struct has been dropped. Instead we know simply employ a non-blocking send over a chan struct. This moves the responsibility of triggering callbacks a level above to the registering client. * Confirmation notifications also now have a counter part in order to notify a caller of the scenario wherein a funding transaction drops out of the chain due to a re-org. A “neagtiveConf” value will be sent to the client over a channel in this case. This will allow a caller to re-register for another confirmation notification. Note that due to this scenario, callers should also register for notifications concerning spends of the counterparty’s inputs to the funding transaction. If a second spend (other than the funding) is detected, the channel should be closed immediately. * Notifications concerning spends now also include the spending transaction, hash, and the input on the spending transaction at which the outpoint is spent.		2016-02-26 17:38:30 -08:00
..
btcdnotify	update imports to github	2016-01-16 10:45:54 -08:00
chainntfs_test.go	Create skeleton for chain notifications	2015-12-16 14:38:21 -06:00
chainntfs.go	chainntfs: expand ChainNotifier interface	2016-02-26 17:38:30 -08:00