luxfi/cli

mirror of https://github.com/luxfi/cli.git synced 2026-10-30 17:01:20 +00:00

Files

T

zeekayandHanzo Dev 62d5f28c22 A chain address is built in one place

The node moved every chain route from /v1/bc/<alias> to /v1/chain/<alias>
and deleted the old prefix, so every chain call answered 404. The address
was spelled out at 112 sites across 34 files and constants.ChainAliasPrefix
was used at none of them, which is why nothing failed to compile when the
segment moved.

route.Chain(uri, alias) composes it now, and route.Alias reads one back,
replacing three hand-rolled parsers — one of which took the alias by
position in the split path and only worked because the new segment happens
to leave the component count unchanged.

TestChainAddressBuiltOnlyHere walks every .go file in the module and fails
on a chain address in a string literal, so the segment cannot drift back;
prose is free to name a route. TestGuardCatchesEachShape plants each
forbidden shape and requires the guard to find it.

The endpoint box and the eleven-chain table were the same list written
twice; there is one list, rendered once, measured rather than hand-padded.
The generated CLI reference and the faucet manifest compose through the
same function.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-30 15:05:42 -07:00

4.5 KiB

Raw Permalink Blame History

Loading Existing State with Lux CLI

The Lux CLI now supports loading existing blockchain state when starting a network. This is particularly useful for:

Resuming from previous network runs
Loading production database snapshots
Testing with real blockchain data
Migrating between different environments

Quick Start

Automatic Detection

If you have an existing mainnet-regenesis database (9.3GB with 1,074,616 blocks), the CLI will automatically detect and load it:

./bin/lux network start

The CLI will look for the database at: ~/.lux-cli/runs/mainnet-regenesis/node1/chains/2G8mK7VCZX1dV8iPjkkTDMpYGZDCNLLVdTJVLmMsG5ZV7zKVmB/db

Manual Specification

You can also explicitly specify the database path:

# Load specific chain database
./bin/lux network start \
  --chain-state-path="/path/to/database/db" \
  --blockchain-id="2G8mK7VCZX1dV8iPjkkTDMpYGZDCNLLVdTJVLmMsG5ZV7zKVmB"

# Load from chaindata directory
./bin/lux network start \
  --state-path="/home/z/work/lux/state/chaindata/lux-mainnet-96369"

Command Line Flags

The following flags are available for state loading:

Flag	Description	Example
`--chain-state-path`	Path to existing chain database	`/path/to/chains/blockchainID/db`
`--state-path`	Path to existing state directory	`~/work/lux/state/chaindata/lux-mainnet-96369`
`--chain-id`	Chain ID for the loaded state	`chain-1234...`
`--blockchain-id`	Blockchain ID for the loaded state	`2G8mK7VCZX1dV8iPjkkTDMpYGZDCNLLVdTJVLmMsG5ZV7zKVmB`

Database Locations

The CLI looks for databases in these locations:

Default mainnet-regenesis: ~/.lux-cli/runs/mainnet-regenesis/node1/chains/[blockchainID]/db
State chaindata: ~/work/lux/state/chaindata/[network]/db
Custom path: Any path you specify with --chain-state-path

Known Blockchain IDs

Network	Blockchain ID	Description
LUX Mainnet	2G8mK7VCZX1dV8iPjkkTDMpYGZDCNLLVdTJVLmMsG5ZV7zKVmB	Primary chain with 1M+ blocks
LUX Testnet	2sdADEgBC3NjLM4inKc1hY1PQpCT3JVyGVJxdmcq6sqrDndjFG	Test chain

Verification

After starting the network with existing state, you can verify the database was loaded:

Check the logs for confirmation messages:

Found existing mainnet-regenesis database at default location
Successfully loaded existing chain state for blockchain 2G8mK7VCZX1dV8iPjkkTDMpYGZDCNLLVdTJVLmMsG5ZV7zKVmB

Query the blockchain to check block height:

curl -X POST --data '{
  "jsonrpc": "2.0",
  "method": "eth_blockNumber",
  "params": [],
  "id": 1
}' -H "Content-Type: application/json" http://localhost:9630/v1/chain/C/rpc

Check database size in the running network:

du -sh ~/.lux-cli/runs/*/node1/chains/*/db

Troubleshooting

Database Not Found

If the database is not automatically detected:

Verify the path exists: ls -la /path/to/database
Check permissions: ls -ld /path/to/database
Use explicit path with --chain-state-path

Wrong Blockchain ID

If you see an error about blockchain ID:

Check the actual blockchain ID from the path
Specify it explicitly with --blockchain-id

Copy Failures

If database copying fails:

Ensure sufficient disk space: df -h
Check write permissions in target directory
Verify source database is not corrupted

Implementation Details

The state loading feature:

Detects existing databases before network start
Copies the database to the appropriate node directory
Preserves all block data, state trie, and transaction history
Maintains database integrity during the copy process
Falls back gracefully if no state is found

Example Use Cases

Resume After Network Restart

# Network was previously running with data
./bin/lux network start  # Automatically loads previous state

Load Production Snapshot

# Load a production database snapshot for testing
./bin/lux network start \
  --chain-state-path="/backup/production-snapshot/db" \
  --blockchain-id="2G8mK7VCZX1dV8iPjkkTDMpYGZDCNLLVdTJVLmMsG5ZV7zKVmB"

Migrate Between Environments

# Move database from one environment to another
./bin/lux network start \
  --state-path="/migration/source/chaindata/lux-mainnet-96369"

Performance

Loading existing state:

9.3GB database: ~30-60 seconds copy time
1M+ blocks: Immediate availability after copy
No replay or reprocessing required
Full state trie preserved

4.5 KiB Raw Permalink Blame History