Files
mpc/config.yaml
zeekayandGitHub d4ce770f4e env: drop LUX_ prefix from env vars (noise) (#8)
Renames:
- LUX_ALLOW_FAKE_TFHE_FOR_TESTING_ONLY -> ALLOW_FAKE_TFHE_FOR_TESTING_ONLY
  (test opt-in for the placeholder UNSAFE TFHE primitive)
- LUX_MPC_CONFIG -> MPC_CONFIG (docs/compose env)
- LUX_MPC_MODE   -> MODE        (Viper config key 'mode' override)

The brand prefix was noise; the env var names speak for themselves.
README/LLM/config docs updated to reflect that Viper has no env prefix
configured (AutomaticEnv reads uppercased config keys directly), so the
prior 'LUX_MPC_*' documentation was inaccurate.

Note: file format magic in pkg/kvstore/zap_backup.go remains
"LUX_MPC_BACKUP" — that's an on-disk format identifier, not an env var.
Renaming it would invalidate every existing backup file.

BREAKING: external callers/operators must update their environment
variable names. Per CLAUDE.md no-backwards-compatibility rule, the old
forms are removed.
2026-05-15 16:01:13 -07:00

31 lines
877 B
YAML

# MPC Node Configuration
# Env vars override everything: MPC_THRESHOLD, ENVIRONMENT, etc. (uppercased config keys via Viper AutomaticEnv).
# Production: all secrets from KMS via --hsm-provider=env or --hsm-provider=aws
mode: consensus
environment: local # mainnet | testnet | local
# Consensus
mpc_threshold: 2
max_concurrent_keygen: 2
# Storage (SQLite default — no external DB needed)
# Set --api-db to a postgres:// URL to switch to PostgreSQL.
db_path: "."
# Backup
backup_enabled: true
backup_period_seconds: 300
backup_dir: backups
# Key material
event_initiator_pubkey: "c3f3511cd2f849fd61e81ea62a842fd33367ee8fb5b867bb900877c7fb72ce3b"
## NATS (legacy mode only — deprecated, used only with --mode=legacy)
# nats:
# url: nats://127.0.0.1:4222
## Consul (legacy mode only — deprecated, used only with --mode=legacy)
# consul:
# address: localhost:8500