Jędrzej Stuczyński
d4ace76273
wip: made storage mostly generic minus modules
changed error types to make modules dyn compatible
implemented traits for sqlite instance
using sqlite instance for rewarder and chain watcher
psql scaffolding
initial postgres support - missing some proto -> json parsing
use postgres in chain scraper
added message registry to block processor
message content parsing in psql
involved addresses
adding null value for logs
Revert "use postgres in chain scraper"
This reverts commit 83c84bfd2d.
using SignerInfo proto definitions for db serialisation
added ibc messages to MessageRegistry
1007 B
1007 B
Nyxd Scraper
Pruning
Similarly to cosmos-sdk, we incorporate pruning into our (scraped) chain data. We attempt to follow their strategies as closely as possible for convenience's sake. Therefore, the following are available:
Strategies
The strategies are configured in config.toml, with the format pruning = "<strategy>" where the options are:
default: only the last 362,880 states(approximately 3.5 weeks worth of state) are kept; pruning at 10 block intervalsnothing: all historic states will be saved, nothing will be deleted (i.e. archiving node)everything: 2 latest states will be kept; pruning at 10 block intervals.custom: allow pruning options to be manually specified throughpruning.keep_recent, andpruning.interval
Custom Pruning
These are applied if and only if the pruning strategy is custom:
pruning.keep_recent: N means to keep all of the last N blockspruning.interval: N means to delete old block data from disk every Nth block.