Toml format (old)

The default config.toml file should look like the following:

[cosmos]
  modules = []
  prefix = "cosmos"

[database]
  host = "localhost"
  max_idle_connections = 1
  max_open_connections = 1
  name = "database-name"
  password = "password"
  port = 5432
  schema = "public"
  ssl_mode = ""
  user = "user"

[grpc]
  address = "localhost:9090"
  insecure = true

[logging]
  format = "text"
  level = "debug"

[parsing]
  fast_sync = false
  genesis_file_path = ""
  listen_new_blocks = true
  parse_genesis = true
  parse_old_blocks = true
  start_height = 1
  workers = 1

[pruning]
  interval = 10
  keep_every = 500
  keep_recent = 100

[rpc]
  address = "http://localhost:26657"
  client_name = "juno"
  max_connections = 20

[telemetry]
  enabled = false
  port = 500

Let's see what each section refers to:

cosmos
pricefeed
rpc
grpc
parsing
database
pruning
logging
telemetry

`cosmos`

This section contains the details of the chain configuration regarding the Cosmos SDK.

Attribute	Type	Description	Example
`modules`	`array`	List of modules that should be enabled	`[ "auth", "bank", "distribution" ]`
`prefix`	`string`	Bech 32 prefix of the addresses	`cosmos`

Supported modules

Currently, we support the followings Cosmos modules:

auth to parse the x/auth data
bank to parse the x/bank data
consensus to parse the consensus data. This includes:
- the genesis details
- average block times (since genesis, in a day, in an hour, in a minute)
distribution to parse the x/distribution data
gov to parse the x/gox data
messages to parse the various messages inside a separate table
mint to parse the x/mint data
modules to get the list of enabled modules inside BDJuno
pricefeed to get the token prices
slashing to parse the x/slashing data
staking to parse the x/staking data
history to store historical data. This is currently limited to
- historical price data, stored every time the price changes
- historical account balance, which includes:
  - the available balance
  - the delegated amount
  - the delegation reward
  - the validator commission reward

Module order

When listing the different modules to be used, please note that there is some order that must be respected. In particular:

modules should be listed before every other module
messages should be listed after the modules module and before every other module
distribution must be listed after the staking module

`pricefeed`

This section contains the data used by the pricefeed to fetch the prices using the CoinGecko APIs.

The only field required in this section is the tokens field, which must be an array of objects, each one containing two fields:

name represents the human-readable name of the token
units contains a list of token units, each of them having the following attributes:
- denom
- exponent
- (optional) aliases
- (optional) price_id

Provide a valid price_id

When fetching the various prices of the token, we will try and search for prices based on the price_id of the units that you provide. For this reason, you need to make sure that you provide at least a unit with a price_id that is listed inside the CoinGecko coins list API.

E.g. If you have a token that is named MyToken and is listed inside CoinGecko with the ticker $MTKN and id MyToken, make sure you specify a token unit having denom = "mtkn", price_id = "mytoken" and exponent = 6 (or whatever amount of decimal places your token unit has inside your chain). This will make sure the price is always fetched correctly.

`rpc`

This section contains the details of the chain RPC to which BDJuno will connect.

Attribute	Type	Description	Example
`address`	`string`	Address of the RPC endpoint	`http://localhost:26657`
`client_name`	`string`	Client name used when subscribing to the Tendermint websocket	`bdjuno`
`max_connections`	`int`	Max number of connections that can created towards the RPC node (any value less or equal to `0` means to use the default one instead)	`20`

`grpc`

This section contains the details of the gRPC endpoint that BDJuno will use to query the data.

Attribute	Type	Description	Example
`address`	`string`	Address of the gRPC endpoint	`localhost:9090`
`insecure`	`boolean`	Whether the gRPC endpoint is insecure or not	`false`

`parsing`

Attribute	Type	Description	Example
`listen_new_blocks`	`boolean`	Whether BDJuno should parse new blocks as soon as they get created	`true`
`parse_genesis`	`boolean`	Whether BDJuno needs to parse the genesis state or not	`true`
`parse_old_blocks`	`boolean`	Whether BDJuno should parse old chain blocks or not	`true`
`start_height`	`integer`	Height at which BDJuno should start parsing old blocks	`250000`
`workers`	`integer`	Number of works that will be used to fetch the data and store it inside the database	`5`

`database`

This section contains all the different configurations related to the PostgreSQL database where BDJuno will write the data.

Attribute	Type	Description	Example
`host`	`string`	Host where the database is found	`localhost`
`port`	`integer`	Port to be used to connect to the PostgreSQL instance	`5432`
`name`	`string`	Name of the database to which connect to	`bdjuno`
`user`	`string`	Name of the user to use when connecting to the database. This user must have read/write access to all the database.	`bdjuno`
`password`	`string`	Password to be used to connect to the database instance	`password`
`schema`	`string`	Schema to be used inside the database (default: `public`)	`public`
`ssl_mode`	`string`	PostgreSQL SSL mode to be used when connecting to the database. If not set, `disable` will be used.	`verify-ca`
`max_idle_connections`	`integer`	Max number of idle connections that should be kept open (default: `1`)	`10`
`max_open_connections`	`integer`	Max number of open connections at any time (default: `1`)	`15`

`pruning`

This section contains the configuration about the pruning options of the database. Note that this will have an effect only if you add the "pruning" entry to the modules field of the cosmos config.

Attribute	Type	Description	Example
`interval`	`integer`	Number of blocks that should pass between one pruning and the other (default: prune every `10` blocks)	`100`
`keep_every`	`integer`	Keep the state every `nth` block, even if it should have been pruned	`500`
`keep_recent`	`integer`	Do not prune this amount of recent states	`100`

`logging`

This section allows to configure the logging details of BDJuno.

Attribute	Type	Description	Example
`format`	`string`	Format in which the logs should be output (either `json` or `text`)	`json`
`level`	`string`	Level of the log (either `verbose`, `debug`, `info`, `warn` or `error`)	`error`

`telemetry`

This section allows to configure the telemetry details of Juno.

Attribute	Type	Description	Example
`enabled`	`bool`	Whether the telemetry should be enabled or not	`false`
`port`	`uint`	Port on which the telemetry server will listen	`8000`

tip

If the telemetry server is enabled, a new endpoint at the provided port and path /metrics will expose Prometheus data.

cosmos​

Supported modules​

pricefeed​

rpc​

grpc​

parsing​

database​

pruning​

logging​

telemetry​