REST API

[mvandeberg]

We want to add a REST API to Koinos. The two big reasons behind this are:

1. Swagger documentation of a REST API makes documenting the API easy with great features (such as embedded interaction).
2. A REST API should be designed to be more user friendly than the JSON-RPC or gRPC APIs. This is needed for improving data access to exchanges, CMC, and CG.

We are going to use Roamin's REST service as a base for our REST API. It is well structured, documented, and works. No need to reinvent the wheel when we have something working already. But there are changes we want to make to his API.

• Change the /api prefix to /v1 #2
• Turn off hosting the website (optionally is ok) #3
• Nonce APIs should have a decode option to return the nonce as an integer #4
• Rename ft to token #5
• Remove specific contracts (KoinDX, Nicknames, KAP, etc.) #6
• When calling a contract, allow resolution of the contract name in the path (i.e. koin would resolve to the KOIN contract using the system contract lookup and other contracts could resolve using nicknames or KAP) #7
• Add a dynamic path /contracts/{contract-id}/{method} that would accept JSON arguments and would use the contract ABI to resolve to a contract method and encode the arguments automatically. The return would be decoded using the ABI and returned as JSON. (Note: this feature will only work with contracts that use the koilib style ABI to use protobuf-js) #8
• Add path overrides for the dynamic path above for KOIN, VHP, and the Claim contract using the proto-js generated types to interact with those contracts. (Other system contracts can be added later) #9

[mvandeberg]

Removing #3 as a requirement for this story. It is a nice to have.