Revert "Supports tags filter for nodes"

Author: kompotkot

nodes/node_balancer/README.md

@@ -1,49 +1,17 @@
 # Node Balancer application
 
-## Installation and configuration
+# Installation
 
--   Prepare environment variables, according with `sample.env`.
+-   Prepare environment variables
 -   Build application
 
 ```bash
 go build -o nodebalancer .
 ```
 
--   Generate configuration
+# Work with nodebalancer
 
-```bash
-nodebalancer generate-config
-```
-
--   Modify configuration. Tags should NOT repeat blockchain, as it is specified in `blockchain` key. Example of configuration:
-
-```bash
-[
-  {
-    "blockchain": "ethereum",
-    "endpoint": "http://127.0.0.1:8545",
-	"tags": ["local"]
-  },
-  {
-    "blockchain": "ethereum",
-    "endpoint": "http://127.0.0.1:9585",
-	"tags": ["local"]
-  },
-  {
-	"blockchain": "ethereum",
-    "endpoint": "https://cool-name.quiknode.pro/y0urn0de1den1f1cat0r/",
-	"tags": ["external"]
-  }
-]
-```
-
-So if with request will be specified tag `local` will be returned node with corresponding tag.
-
-## Work with nodebalancer
-
-**IMPORTANT** Do not use flag `-debug` in production.
-
-### add-access
+## add-access
 
 Add new access for user:
 
@@ -57,7 +25,7 @@ nodebalancer add-access \
 	--blockchain--access true
 ```
 
-### delete-access
+## delete-access
 
 Delete user access:
 
@@ -69,7 +37,7 @@ nodebalancer delete-access \
 
 If `access-id` not specified, all user accesses will be deleted.
 
-### users
+## users
 
 ```bash
 nodebalancer users | jq .
@@ -99,7 +67,7 @@ This command will return a list of bugout resources of registered users to acces
 
 `extended_methods` - boolean which allow you to call not whitelisted method to blockchain node, by default for new user this is equal to `false`
 
-### server
+## server
 
 ```bash
 nodebalancer server -host 0.0.0.0 -port 8544 -healthcheck
@@ -108,17 +76,17 @@ nodebalancer server -host 0.0.0.0 -port 8544 -healthcheck
 Flag `--healthcheck` will execute background process to ping-pong available nodes to keep their status and current block number.
 Flag `--debug` will extend output of each request to server and healthchecks summary.
 
-## Work with node
+# Work with node
 
 Common request to fetch block number
 
 ```bash
-curl --request POST 'http://127.0.0.1:8544/nb/ethereum/jsonrpc?access_id=<access_id>&data_source=<blockchain/database>' \
+curl --request GET 'http://127.0.0.1:8544/nb/ethereum/jsonrpc?access_id=<access_id>&data_source=<blockchain/database>' \
     --header 'Content-Type: application/json' \
     --data-raw '{
         "jsonrpc":"2.0",
         "method":"eth_getBlockByNumber",
-        "params":["latest", false],
+        "params":["0xb71b64", false],
         "id":1
     }'
 ```
@@ -129,16 +97,3 @@ For Web3 providers `access_id` and `data_source` could be specified in headers
 --header 'x-node-balancer-data-source: <blockchain/database>'
 --header 'x-node-balancer-access-id: <access_id>'
 ```
-
-Same request to fetch specific nodes using tags
-
-```bash
-curl --request POST 'http://127.0.0.1:8544/nb/ethereum/jsonrpc?access_id=<access_id>&data_source=<blockchain/database>&tag=<specific_tag_1>&tag=<specific_tag_2>' \
-    --header 'Content-Type: application/json' \
-    --data-raw '{
-        "jsonrpc":"2.0",
-        "method":"eth_getBlockByNumber",
-        "params":["latest", false],
-        "id":1
-    }'
-```