60 isolate connector

[0xp3gasus]

Description

Connector can be isolated from blockchain nodes. It supports multiple tokens at the same time in differents networks. With the Admin package created, it is posible to add, update and remove tokens in differents networks. The rest of the functionality of the connector is the same.

Endpoint paths have been replace from /rpc and /ws to {coin}/{network}/rpc and /{coin}/network}/ws

Fixes #60

Dependencies (if any)

None

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] This change requires a documentation update

How Has This Been Tested?

• Adding ETH Token in regtest network to connector

  Request

  curl --location --request POST 'http://localhost:80/admin/addCoin' \
  --header 'Origin: http://localhost' \
  --header 'Access-Control-Request-Method: POST' \
  --header 'Access-Control-Request-Headers: access-control-allow-origin,content-type' \
  --header 'Sec-Fetch-Mode: cors' \
  --header 'Sec-Fetch-Site: same-site' \
  --header 'Sec-Fetch-Dest: empty' \
  --header 'Referer: http://localhost' \
  --header 'Accept-Language: es,en-GB;q=0.9,en-US;q=0.8,en;q=0.7' \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "coin": "eth",
      "network": "regtest",
      "config": {
          "rpcPort": 8546,
          "wsPort": 8546
      }
  }'

  Response

  {
      "success": true,
      "message": "regtest network added for currency eth"
  }

• Getting ETH config

  Request

  curl --location --request POST 'http://localhost:80/admin/getCoin' \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "coin": "eth",
      "network": "regtest"
  }'

  Response

  {
      "success": true,
      "message": "Config configuration for regtest network for currency eth retrieved successfully",
      "coin": "eth",
      "network": "regtest",
      "config": {
          "protocol": "http",
          "host": "ethereumgo",
          "rpcPort": 8546,
          "wsPort": 8546
      }
  }

• Removing ETH token in regtest network from connector

  Request

  curl --location --request POST 'http://localhost:80/admin/removeCoin' \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "coin": "eth",
      "network": "regtest"
  }'

  Response

  {
      "success": true,
      "message": "regtest network removed for currency eth"
  }

• Making RPC request to ETH token in regtest network when it is not added to connector

  Request

  curl --location --request POST 'http://localhost:80/eth/regtest/rpc' \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "id": 1609070896412,
      "method": "getHeight",
      "params": {},
      "jsonrpc": "2.0"
  }'

  Response

  {
      "message": "Currency eth has not been previously added",
      "code": 404
  }

• Making RPC request to ETH token in regtest network when it is added to connector

  Request

  curl --location --request POST 'http://localhost:80/eth/regtest/rpc' \
  --header 'Content-Type: application/json' \
  --data-raw '{
      "id": 1609070896412,
      "method": "getHeight",
      "params": {},
      "jsonrpc": "2.0"
  }'

  Response

  {
      "id": 1609070896412,
      "jsonrpc": "2.0",
      "result": {
          "latestBlockIndex": "6",
          "latestBlockHash": "0x687fab92aba99fce014e97c68b3acf41c42ee0b9ae30f0a198408fd5938781c0"
      }
  }

• Wesockets subscribe to New Blocks Topic in ETH token in regtest mode

  Endpoint: ws://localhost:80/eth/regtest/ws

  Request

  {
      "id": 1,
      "method": "subscribeToNewBlocks",
      "jsonrpc": "2.0",
      "params": {}
  }

  Response

  {
      "id": 1, 
      "jsonrpc": "2.0", 
      "result": {
          "subscribed": true
      }
  }

Test Configuration:

• Operating system (output of sw_vers): macOS 12.0.1

Good practices to consider

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

[phoenix-web3]

This PR is huge, @hippocampusSwapper and @bridgedragon should review this PR