From b2522ef75ad35f6b15eae490a6f2b36cdff44207 Mon Sep 17 00:00:00 2001
From: Olaoluwa Osuntokun <laolu32@gmail.com>
Date: Wed, 16 Dec 2015 14:38:21 -0600
Subject: [PATCH] Create skeleton for chain notifications

* Goal is to backend agnostic source to chain notifications
* Open channels will communicate with this source to register intent
for critical notifications
* Pending notifications will need to be committed to disk.
* Will also need a journal to ensure no notification is missed
* Later goals include extending this to communicate with 3rd party
outsource services
---
 chainntfs/chainntfs.go      | 12 ++++++++++++
 chainntfs/chainntfs_test.go |  1 +
 2 files changed, 13 insertions(+)
 create mode 100644 chainntfs/chainntfs.go
 create mode 100644 chainntfs/chainntfs_test.go

diff --git a/chainntfs/chainntfs.go b/chainntfs/chainntfs.go
new file mode 100644
index 000000000..5e78787f3
--- /dev/null
+++ b/chainntfs/chainntfs.go
@@ -0,0 +1,12 @@
+package chainntnfs
+
+// TODO(roasbeef): finish
+//  * multiple backends for interface
+//   * btcd - websockets
+//   * core - rpc polling or ZeroMQ
+//   * direct p2p
+//   * random bitcoin API?
+//   * electrum?
+//   * other stuff maybe...
+type ChainNotifier interface {
+}
diff --git a/chainntfs/chainntfs_test.go b/chainntfs/chainntfs_test.go
new file mode 100644
index 000000000..54a8429f6
--- /dev/null
+++ b/chainntfs/chainntfs_test.go
@@ -0,0 +1 @@
+package chainntnfs