Summary

At the time of this writing, there are 181 tokens listed on Binance Chain. In order to build "Asset" page in our Mintscan, custom API is needed to be built which provide necessary data following how it is designed.

This API returns tokens list and it has only the following parameters:

• Mintable
• Name
• Original Symbol
• Owner
• Symbol
• Total Supply

Params that further needed

• Asset Price
• Asset Detail Info like social profiles and description (if possible)
• Asset Holders
• Asset Image / Logo

Note: asset image can be found from this repo

Decision

For now, we decided to use an official explorer asset API although it is not for public use I believe.
We will need to find a way to gather necessary data to build our own custom API for this.

Issue

There is performance Issue when counting all transactions which are saved in database.
As there will be more transactions to count as time goes, this problem needs to be solved.

Possible solution

1. Create a cron job that counts transactions and save it in other table.

Summary

Having a meaningful documentation of APIs is important for other users; however, this is not an imminent issue right now. This feature will be supported later.

Generate Swagger docs for Documenting Mintscan APIs.

Migrating the APIs that rely on Binance Explorer API

Migration for the below APIs is needed since their explorer API is not public.

• Asset API
• Assets API
• AssetHolders API
• AccountTxs API

We decided to use those APIs at first because of the following reasons.

• We had hard time getting some of the data from HTTP API and API Server.
• We simply thought why not using Explorer API since HTTP API itself is also controlled and operated by Binance team.

In the long run, these APIs should be migrated. It is good for our Mintscan for Binance Chain and Binance Explorer API server.

Summary

The title itself is self-explanatory. Chain Exporter needs to be prevented from a single point of failure meaning that when one RPC node is down, it should try to connect to other RPC nodes.

Problem Definition

A public RPC node that is available by Binance team is sometimes down for handling heavy traffic.

Describe the solution you'd like

Add support to reconnect to other RPC nodes when one it down.

config.yaml

network_type: "testnet"

mainnet:
  node: 
    rpc_node: "tcp://localhost:26657/" # tcp://dataseed1.binance.org:80
    accelerated_node: "http://localhost:1317/" # https://dex-asiapacific.binance.org/api/v1
    api_server_endpoint: "http://localhost:1317/"
    explorer_server_endpoint: "https://explorer.binance.org/api/v1" # https://explorer.binance.org/api/v1
  database:
    host: "localhost"
    port: 5432
    user: "postgres"
    password: "1234"
    table: ""
  market:
    coingecko_endpoint: ""

testnet:
  node: 
    rpc_node: "tcp://localhost:26657" # tcp://dataseed1.binance.org:80
    accelerated_node: "http://192.168.1.112:1317" # https://dex-asiapacific.binance.org/api/v1
    api_server_endpoint: "http://192.168.1.112:1317"
    explorer_server_endpoint: "https://explorer.binance.org/api/v1"
  database:
    host: "localhost"
    port: 5432
    user: "postgres"
    password: "1234"
    table: ""
  market:
    coingecko_endpoint: ""

error

Chain Exporter 2022/03/02 00:50:37 exporter.go:76: Starting Chain Exporter...
Chain Exporter 2022/03/02 00:50:37 exporter.go:77: Version: 1.2.0-16-g9ae4ea1 | Commit Hash: 9ae4ea1dd0babbdda46ebade497156f47cee413b
Chain Exporter 2022/03/02 00:50:37 exporter.go:81: start - sync blockchain
panic: http: invalid pattern

goroutine 61 [running]:
net/http.(*ServeMux).Handle(0x51311e0, {0x0, 0x0}, {0x4b62960, 0xc000611dd0})
        /usr/local/go/src/net/http/server.go:2435 +0x24c
net/http.Handle(...)
        /usr/local/go/src/net/http/server.go:2484
github.com/cosmostation/mintscan-binance-dex-backend/chain-exporter/prometheus.StartMetricsScraping({{0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}})
        /Users/jarupaksrisuchat/Documents/github/mintscan-binance-dex-backend/chain-exporter/prometheus/metrics.go:38 +0x65
created by github.com/cosmostation/mintscan-binance-dex-backend/chain-exporter/exporter.NewExporter
        /Users/jarupaksrisuchat/Documents/github/mintscan-binance-dex-backend/chain-exporter/exporter/exporter.go:63 +0x32b

Feature

The official block explorer shows each block's reward fee. I haven't successfully got to know how fees are calculated in each block so far, but discussion is needed if this data is significant enough to show in our Mintscan.

References

• Docs regarding fees: https://docs.binance.org/trading-spec.html#fees
• Fee API: https://dex.binance.org/api/v1/fees?format=amino