2. Node Deployment & Configuration

Q: When configuring Maker liquidity pools (e.g., POOLS_BTC_*), why does the node panic on startup with the error address not match with mnemonic?

A: This usually occurs because the derivation path index of the mnemonic exceeds the node's scanning range. Currently, the Nexus engine is hardcoded to scan up to index 20 (i.e., scanning from m/86'/0'/0'/0/0 to m/86'/0'/0'/0/20). Please ensure your address is generated within this 0-20index limit.

Q: Can I set a private key directly for Maker pools via environment variables (like PRIVATE_KEY_HEX), similar to the Taker configuration?

A: No, you cannot. There is no equivalent private key variable for Maker pools. To maintain standard deterministic key management for liquidity pools, the system relies strictly on the mnemonic derivation provided in the .env file.

Q: Will the system automatically start market-making once the local node is spun up with the configured pool addresses?

A: No. After your Nexus service is successfully running, an upstream enrollment step is required. You must manually register and initialize the pool configuration on the Web Dashboard / Composer before the system actively accepts the pool.