162 method in response

[0xp3gasus]

Description

Response payloads do not response methods or currencies. HTTP, RPC and WS methods registration has been improve.

Fixes #162

Dependencies (if any)

None

Type of change

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] 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?

• Test A. Calling ETH Method over RPC

  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"
  }'

  {
      "id": 1609070896412,
      "jsonrpc": "2.0",
      "result": {
          "latestBlockIndex": "14617285",
          "latestBlockHash": "0x23e3930172383f71dd1c2e3a288e724586cdea3e5bc33dde152b356f70dbf3d6"
      }
  }

• Test B. Calling ETH Method over HTTP

  curl --location --request GET 'http://localhost:80/eth/regtest/getHeight'

  {
      "latestBlockIndex": "14617291",
      "latestBlockHash": "0x7a7c67926773e4eafb45a9f810f4e83eb2d68f86305d47f3f335bc90139f4c21"
  }

• Test C. Calling ETH WS method

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

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

• Test E. Calling ETH unknown method

  curl --location --request POST 'http://localhost:80/eth/regtest/getAddressBalancee' \
      --header 'Content-Type: application/json' \
      --data-raw '{
              "address": "0x625ACaEdeF812d2842eFd2Fb0294682A868455bd"
      }'

  {
      "message": "Not found",
      "code": 404
  }

• Test D. Calling ETH method with different HTTP method

  curl --location --request GET 'http://localhost:80/eth/regtest/getAddressBalance' \
      --header 'Content-Type: application/json' \
      --data-raw '{
            "address": "0x625ACaEdeF812d2842eFd2Fb0294682A868455bd"
     }'

  {
      "message": "Method not allowed",
      "code": 405
  }

• Test F. Calling BTC Method over RPC

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

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

• Test G. Calling BTC Method over HTTP

  curl --location --request POST 'http://localhost:80/btc/regtest/getHeight'

  {
      "latestBlockIndex": "0",
      "latestBlockHash": "0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206"
  }

• Test H. Calling BTC WS method

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

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

• Test I. Calling BTC unknown method

  curl --location --request POST 'http://localhost:80/btc/regtest/getHeightttt'

  {
      "message": "Not found",
      "code": 404
  }

• Test J. Calling BTC method with different HTTP method

  curl --location --request POST 'http://localhost:80/btc/regtest/getHeight'

  {
      "message": "Method not allowed",
      "code": 405
  }

Test Configuration:

• Operating system (output of cat /etc/os-release): macOS 12.2.1
• Kernel version (output of uname -sr): Darwin 21.3.0
• Architecture (output of uname -m): x86_64

Related PR or Docs PR

Docs PR related # Other PR related #

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
• [x] 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
• [x] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules