mirror of
https://github.com/luxfi/bridge.git
synced 2026-09-24 00:26:46 +00:00
zeekay
83f826794a
The .network host was retired 2026-07-27 and no longer resolves at all, so every reference to it named an address that cannot answer. The brand host is .cloud, matching kms.zoo.cloud and the rest of the white-label convention. Left alone deliberately, because rewriting them would invert what they say: the LLM.md line that RECORDS the retirement, the e2e spec that ASSERTS kms.lux.network must not resolve, and the recorded applies + cluster backups, which are faithful accounts of what was applied and are not config.
29 lines
981 B
YAML
29 lines
981 B
YAML
# Lux KMS Configuration for MPC Nodes
|
|
# Add these settings to your existing config.yaml
|
|
|
|
# Lux KMS Integration Settings
|
|
kms:
|
|
# For local Lux KMS instance (if running ~/work/lux/kms locally)
|
|
site_url: "http://localhost:8080"
|
|
|
|
# For production Lux KMS
|
|
# site_url: "https://kms.lux.cloud"
|
|
|
|
# Project settings (required)
|
|
project_id: "your-project-id" # Or set KMS_PROJECT_ID env var
|
|
environment: "prod" # Options: dev, staging, prod
|
|
secret_path: "/mpc" # Path where MPC secrets will be stored
|
|
|
|
# Authentication options:
|
|
|
|
# Option 1: Service Token (simplest)
|
|
# Set KMS_TOKEN environment variable
|
|
|
|
# Option 2: Universal Auth (recommended for production)
|
|
# Create a machine identity in Lux KMS and use its credentials
|
|
client_id: "your-client-id"
|
|
client_secret: "your-client-secret"
|
|
|
|
# Example environment variables to set:
|
|
# export KMS_PROJECT_ID="651c...your-project-id"
|
|
# export KMS_TOKEN="st.your-service-token" # If using service token auth |