iov-one / bns Goto Github PK

We need to include an endpoint for balances. We want an endpoint that responds with data like from BNSCLI_TM_ADDR=http://167.172.104.185:31140 bnscli query -path '/wallets' -data C1721181E83376EF978AA4A9A38A5E27C08C7BB2 eg.

{
  "Key": "636173683ac1721181e83376ef978aa4a9a38a5e27c08c7bb2",
  "Value": {
    "metadata": {
      "schema": 1
    },
    "coins": [
      {
        "whole": 9773,
        "fractional": 550000000,
        "ticker": "IOV"
      }
    ]
  }
}

The endpoint should be /cash/balances and list all balances when no parameter is given and should list a single balance if given an owner parameter in either hex or bech32 format.

We just got word that Cosmostation would like to be able to submit signed transactions through the bnsapi. Adding that functionality is top priority list.

We need to check if exchangenet(v0.21.x) has any features missing

Summary:
URL and PORt are not correctly identified

Steps to Reproduce:

Expected result:

Actual result:

Use the Common Log Format (https://www.graylog.org/post/log-formats-a-complete-guide)

Currently, if you browse to the bnsapi without specifying an endpoint you see

{
	"errors": [
		"Not Found"
	]
}

We need a structured endpoint listing such as cosmos:

Available endpoints:
Endpoints that require arguments:
//63.35.133.166/abci_info?
//63.35.133.166/abci_query?path=_&data=_&height=_&prove=_
//63.35.133.166/block?height=_
//63.35.133.166/block_results?height=_
//63.35.133.166/blockchain?minHeight=_&maxHeight=_
//63.35.133.166/broadcast_evidence?evidence=_
//63.35.133.166/broadcast_tx_async?tx=_
//63.35.133.166/broadcast_tx_commit?tx=_
//63.35.133.166/broadcast_tx_sync?tx=_
//63.35.133.166/commit?height=_
//63.35.133.166/consensus_params?height=_
//63.35.133.166/consensus_state?
//63.35.133.166/dump_consensus_state?
//63.35.133.166/genesis?
//63.35.133.166/health?
//63.35.133.166/net_info?
//63.35.133.166/num_unconfirmed_txs?
//63.35.133.166/status?
//63.35.133.166/subscribe?query=_
//63.35.133.166/tx?hash=_&prove=_
//63.35.133.166/tx_search?query=_&prove=_&page=_&per_page=_
//63.35.133.166/unconfirmed_txs?limit=_
//63.35.133.166/unsubscribe?query=_
//63.35.133.166/unsubscribe_all?
//63.35.133.166/validators?height=_

Acceptance:

• Endpoints with and w/o parameters must be shown separately
• Listed endpoints should be links, not just plain text

We need a REST API endpoint that lists all the msgfees like we have for escrows, eg http://exchangenet-bnsapi.iov.one/escrow/escrows.

The endpoint should be: http://exchangenet-bnsapi.iov.one/msgfee/msgfees

• The endpoint format of /singular/plural and that it doesn't have a trailing slash.

• fix the title --> IOV Name Service Rest API

• only display endpoint which is relevant for mainnet (cash, info, usernames/owner, usernames/iovstarname)

• for the cash/balances endpoint

  • instead of 'Returns a bnsd/username.Token entitiies" ' you should say
    "returns balances based on iov address"

• for the username/orkun*iov endpoint

  • you should say "Resolve an iov starname'

• for the username/owner endpoint

  • you should say "Returns the list of iov starname owned by this iov address"

• fix the Models section

the env var DOMAN should be HOST and we need to add PORT, so that the available endpoints don't 404 localhost. The list of endpoints should be like //HOST:PORT/info/, etc.

• Note the double // is not prefixed with http(s) .

We have too many clusters, and they have confusing names.

Mainnet repo cluster: https://github.com/iov-one/mainnet

The mainnet repo cluster is NOT currently our production cluster; hence it's still a testnet. Once we secure it then Dave will migrate it to be our production cluster.

The REST API endpoints /username/resolve/:starname and /username/owner/:owner only return the iov-mainnet target even when other targets exist. All targets should be returned. (The bnsd v1.0.0 version of the REST API does not suffer from this bug; see the kraken*dave account at http://exchangenet-bnsapi.iov.one:8000/account/accounts?domainKey=dave.)

• http://bnsapi.iov.one:8000/username/resolve/dave*iov must return targets for ETH, LISK, and IOV

curl -X GET "https://bnsapi.cluster-mainnet.iov.one/cash/balances?offset=1" -H "accept: application/json"

yields

{
  "errors": [
    "offset is in wrong format. send integer"
  ]
}

Summary:
When i am on the index page of the bnspi and I click on a link, it is to a broken page
Steps to Reproduce:
When i am on the index page of the bnspi and I click on a link, it is to a broken page
Expected result:
it should display the endpoint
--> Lets use relative links so we don't care about ip address and ports on the index page
Actual result:

You just displayed the list of targets but you don't display the actualy starname names

GET /account/address/nonce/:owner returns nonce based on iov address
GET /account/pubkey/nonce/:owner returns nonce based on iov public key

We should use https:// instead of http:// for our testnet URLs (ex: http://bnsapi.iov.one:8000/) cluster in digital ocean #65

We need to investigate if the bnsapi app can be made compatible with weave v0.21.2, the mainnet version. If it is compatible then we need an endpoint for usernames, just like we already have for accounts.