trimming down to ipfs watchers

documentation/custom-transformers.md

@@ -63,7 +63,7 @@ these are run independently, instead of using `composeAndExecute`, a couple of t
 
 * The `execute` command does not require the plugin transformer dependencies be located in their `$GOPATH` directories,
 instead it expects a .so file (of the name specified in the config file) to be in
-`$GOPATH/src/github.com/vulcanize/vulcanizedb/plugins/` and, as noted above, also expects the plugin db migrations to
+`$GOPATH/src/github.com/vulcanize/ipfs-chain-watcher/plugins/` and, as noted above, also expects the plugin db migrations to
  have already been ran against the database.
 
  * Usage:
@@ -103,7 +103,7 @@ The config provides information for composing a set of transformers from externa
     wsPath   = "ws://127.0.0.1:8546"
 
 [exporter]
-    home     = "github.com/vulcanize/vulcanizedb"
+    home     = "github.com/vulcanize/ipfs-chain-watcher"
     name     = "exampleTransformerExporter"
     save     = false
     transformerNames = [
@@ -137,7 +137,7 @@ The config provides information for composing a set of transformers from externa
         migrations = "to/db/migrations"
         rank = "1"
 ```
-- `home` is the name of the package you are building the plugin for, in most cases this is github.com/vulcanize/vulcanizedb
+- `home` is the name of the package you are building the plugin for, in most cases this is github.com/vulcanize/ipfs-chain-watcher
 - `name` is the name used for the plugin files (.so and .go)   
 - `save` indicates whether or not the user wants to save the .go file instead of removing it after .so compilation. Sometimes useful for debugging/trouble-shooting purposes.
 - `transformerNames` is the list of the names of the transformers we are composing together, so we know how to access their submaps in the exporter map
@@ -174,7 +174,7 @@ The general structure of a plugin .go file, and what we would see built with the
 package main
 
 import (
-	interface1 "github.com/vulcanize/vulcanizedb/libraries/shared/transformer"
+	interface1 "github.com/vulcanize/ipfs-chain-watcher/libraries/shared/transformer"
 	transformer1 "github.com/account/repo/path/to/transformer1"
 	transformer2 "github.com/account/repo/path/to/transformer2"
 	transformer3 "github.com/account/repo/path/to/transformer3"

documentation/super_node/apis.md

@@ -40,10 +40,10 @@ An example of how to subscribe to a real-time Ethereum data feed from the super
     	"github.com/ethereum/go-ethereum/rpc"
     	"github.com/spf13/viper"
     	
-    	"github.com/vulcanize/vulcanizedb/libraries/shared/streamer"
-    	"github.com/vulcanize/vulcanizedb/pkg/eth/client"
-    	"github.com/vulcanize/vulcanizedb/pkg/super_node"
-    	"github.com/vulcanize/vulcanizedb/pkg/super_node/eth"
+    	"github.com/vulcanize/ipfs-chain-watcher/libraries/shared/streamer"
+    	"github.com/vulcanize/ipfs-chain-watcher/pkg/eth/client"
+    	"github.com/vulcanize/ipfs-chain-watcher/pkg/super_node"
+    	"github.com/vulcanize/ipfs-chain-watcher/pkg/super_node/eth"
     )
 
     config, _ := eth.NewEthSubscriptionConfig()
@@ -162,10 +162,10 @@ An example of how to subscribe to a real-time Bitcoin data feed from the super n
     	"github.com/ethereum/go-ethereum/rpc"
     	"github.com/spf13/viper"
     	
-    	"github.com/vulcanize/vulcanizedb/libraries/shared/streamer"
-    	"github.com/vulcanize/vulcanizedb/pkg/eth/client"
-    	"github.com/vulcanize/vulcanizedb/pkg/super_node"
-    	"github.com/vulcanize/vulcanizedb/pkg/super_node/btc"
+    	"github.com/vulcanize/ipfs-chain-watcher/libraries/shared/streamer"
+    	"github.com/vulcanize/ipfs-chain-watcher/pkg/eth/client"
+    	"github.com/vulcanize/ipfs-chain-watcher/pkg/super_node"
+    	"github.com/vulcanize/ipfs-chain-watcher/pkg/super_node/btc"
     )
 
     config, _ := btc.NewBtcSubscriptionConfig()

documentation/super_node/setup.md

@@ -138,9 +138,9 @@ Finally, we can begin the vulcanizeDB process itself.
 
 Start by downloading vulcanizedb and moving into the repo:
 
-`go get github.com/vulcanize/vulcanizedb`
+`go get github.com/vulcanize/ipfs-chain-watcher`
 
-`cd $GOPATH/src/github.com/vulcanize/vulcanizedb`
+`cd $GOPATH/src/github.com/vulcanize/ipfs-chain-watcher`
 
 Run the db migrations against the Postgres database we created for vulcanizeDB: