You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make the default configuration value for whether a node performs indexing to betrue.
Problem Definition
Voyager needs indexing nodes to show transaction history so more indexing nodes are better. There are no real disadvantages since it can be turned off.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
The config.toml generated by gaiad init contains the following stanza:
##### transactions indexer configuration options #####
[tx_index]
# What indexer to use for transactions
#
# Options:
# 1) "null" (default)
# 2) "kv" - the simplest possible indexer, backed by key-value storage (defaults to levelDB; see DBBackend).
indexer = "kv"
# Comma-separated list of tags to index (by default the only tag is tx hash)
#
# It's recommended to index only a subset of tags due to possible memory
# bloat. This is, of course, depends on the indexer's DB and the volume of
# transactions.
index_tags = ""
# When set to true, tells indexer to index all tags. Note this may be not
# desirable (see the comment above). IndexTags has a precedence over
# IndexAllTags (i.e. when given both, IndexTags will be indexed).
index_all_tags = false
It seems indexing is on by default, i.e. indexer = "kv"
Summary
Make the default configuration value for whether a node performs indexing to be
true
.Problem Definition
Voyager needs indexing nodes to show transaction history so more indexing nodes are better. There are no real disadvantages since it can be turned off.
For Admin Use
The text was updated successfully, but these errors were encountered: