zeekay
7cf87b230b
The module already called itself github.com/luxfi/node while containing no node in Go: cmd/luxd was twenty-one lines that printed the size of a few types, and the Go column of the matrix measured a VM plugin. A repo that fetches the thing it claims to be has not replaced it, so the Go sources move in — 1515 files, the daemon and everything under it — and the build reaches outside this module for nothing. Rust and C++ sit beside it unchanged and are still measured against it by the differential. That is the point of one repo: the reference implementation and the two ports are the same checkout, so parity is a thing you can run rather than a thing you assert. Verified: builds, and the closure carries no lux-private — checked at build time rather than believed. The daemon starts twelve chains on a local network (P X C Q Z A B G K M F, plus D through its plugin) and reports healthy.
1.5 KiB
tags, description, pagination_label, sidebar_position
| tags | description | pagination_label | sidebar_position | ||
|---|---|---|---|---|---|
|
Reference for all available X-chain config options and flags. | X-Chain Configs | 2 |
X-Chain
In order to specify a config for the X-Chain, a JSON config file should be
placed at {chain-config-dir}/X/config.json.
For example if chain-config-dir has the default value which is
$HOME/.node/configs/chains, then config.json can be placed at
$HOME/.node/configs/chains/X/config.json.
This allows you to specify a config to be passed into the X-Chain. The default values for this config are:
{
"checksums-enabled": false
}
Default values are overridden only if explicitly specified in the config.
The parameters are as follows:
Transaction Indexing
index-transactions
Boolean
Enables XVM transaction indexing if set to true.
When set to true, XVM transactions are indexed against the address and
assetID involved. This data is available via xvm.getAddressTxs
API.
:::note
If index-transactions is set to true, it must always be set to true
for the node's lifetime. If set to false after having been set to true, the
node will refuse to start unless index-allow-incomplete is also set to true
(see below).
:::
index-allow-incomplete
Boolean
Allows incomplete indices. This config value is ignored if there is no X-Chain indexed data in the DB and
index-transactions is set to false.
checksums-enabled
Boolean
Enables checksums if set to true.