fix: backdate sovereign-apps to 2026-03-03

apps/docs/content/blog/sovereign-apps.mdx

@@ -1,7 +1,7 @@
 ---
 title: "The Operating System for Sovereign Apps"
 description: "Base owns state. Lux owns trust. Providers own service quality. Users own keys and exit rights."
-date: 2026-04-07
+date: 2026-03-03
 author: Zach Kelling
 ---
 

apps/docs/content/docs/api-reference/sdk-js.mdx

@@ -121,7 +121,8 @@ const seed = mnemonic.mnemonicToSeedSync(phrase);
 
 ```typescript
 const keychain = xchain.keyChain();
-keychain.importKey("PrivateKey-ewoqjP7PxY4yr3iLTpLisriqt94hdyDFNgchSxGGztUrTXtNN");
+// Use a key derived from LUX_MNEMONIC -- never use well-known test keys
+keychain.importKey(myPrivateKey);
 
 const addresses = keychain.getAddressStrings();
 console.log("Addresses:", addresses);

apps/docs/content/docs/reference/lux-adx.mdx

@@ -22,7 +22,7 @@ ADX is a **high-performance Connected TV (CTV) ad exchange** designed for 100M+
 ## Hard requirements
 
 1. ALWAYS use `github.com/luxfi/*` packages -- NEVER `go-ethereum` or `luxfi`
-2. NEVER use EWOQ keys -- generate fresh keys
+2. NEVER use well-known test keys -- generate fresh keys via `LUX_MNEMONIC`
 3. FoundationDB 7.3.27+ required for storage backend
 
 ## Key Dependencies

apps/docs/content/docs/reference/lux-ai.mdx

@@ -25,7 +25,7 @@ AI proofs generated on the network can mint tokens on any teleport-supported net
 ## Hard requirements
 
 1. ALWAYS use `github.com/luxfi/*` packages -- NEVER `go-ethereum` or `luxfi`
-2. NEVER use EWOQ keys -- generate fresh keys
+2. NEVER use well-known test keys -- generate fresh keys via `LUX_MNEMONIC`
 3. Desktop requires Rust (for Tauri), Node.js 20+, pnpm
 
 ## Architecture

apps/docs/content/docs/reference/lux-cli.mdx

@@ -215,7 +215,7 @@ Keys are stored in `~/.lux/keys/<name>/` with subdirectories per type:
 
 All key types derived from a single BIP39 mnemonic using HKDF. Keys can be locked/unlocked for session management. Backend system supports multiple storage providers (keychain, file, K-Chain distributed).
 
-NEVER use EWOQ keys. Always generate fresh keys with `lux key create`.
+NEVER use well-known test keys. Always generate fresh keys with `lux key create`.
 
 ## MPC Operations
 

apps/docs/content/docs/reference/lux-corona.mdx

@@ -20,7 +20,7 @@ Corona is the post-quantum signature primitive for Lux consensus. It enables t-o
 ## Hard requirements
 
 1. ALWAYS use `github.com/luxfi/*` packages -- NEVER `go-ethereum` or `luxfi`
-2. NEVER use EWOQ keys
+2. NEVER use well-known test keys -- generate fresh keys via `LUX_MNEMONIC`
 3. Requires `github.com/luxfi/lattice/v7` for all ring polynomial operations
 4. Go packages stay at v1.x.x (the module itself has no version suffix)
 

apps/docs/content/docs/reference/lux-deploy.mdx

@@ -245,7 +245,7 @@ LUX_MNEMONIC="word1 word2 ..." ./deploy-chains \
 2. **Parallel imports**: Block imports run in background with monitoring
 3. **Atomic snapshots**: Network stopped during snapshot for consistency
 4. **Health-first**: Operations verify prerequisites before execution
-5. **No EWOQ keys**: Mnemonic-based key derivation only
+5. **No well-known test keys**: Mnemonic-based key derivation only
 6. **Network separation**: Mainnet and testnet use different ports, never conflict
 7. **CLI-based**: Uses `lux` CLI for network management, never `pkill luxd`
 

apps/docs/content/docs/reference/lux-genesis.mdx

@@ -22,7 +22,7 @@ description: "Documentation for Lux Genesis"
 - Module path: `github.com/luxfi/genesis`
 - All dependencies use `github.com/luxfi/*` packages exclusively -- never `go-ethereum` or `luxfi`
 - Go package versions stay at v1.x.x (no v2+ bumps)
-- Never expose or commit private keys, mnemonics, or EWOQ keys
+- Never expose or commit private keys or mnemonics
 - Treasury address `0x9011E888251AB053B7bD1cdB598Db4f9DEd94714` is canonical across all networks
 
 ## Quick reference

apps/docs/content/docs/reference/lux-lpm.mdx

@@ -21,7 +21,7 @@ LPM is a command-line tool for managing virtual machine binaries and chain defin
 
 1. ALWAYS use `github.com/luxfi/*` packages -- NEVER `go-ethereum` or `luxfi`
 2. Go packages stay at v1.x.x (module is `github.com/luxfi/lpm`, no version suffix)
-3. NEVER use EWOQ keys
+3. NEVER use well-known test keys -- generate fresh keys via `LUX_MNEMONIC`
 4. Requires a running Lux node for VM hot-reload via admin API (optional; works offline too)
 
 ## Quick reference

apps/docs/content/docs/reference/lux-node.mdx

@@ -74,7 +74,7 @@ Lux Node (`luxd`) is the core validator node for the Lux Network -- a multi-chai
 ## Hard requirements
 
 1. **ALWAYS** use `github.com/luxfi/*` packages -- **NEVER** `go-ethereum` or `luxfi`
-2. **NEVER** use EWOQ keys -- generate fresh keys for every deployment
+2. **NEVER** use well-known test keys -- generate fresh keys for every deployment
 3. **NEVER** `pkill luxd` -- use `lux cli` or send SIGINT/SIGTERM for graceful shutdown
 4. **NEVER** bump Go packages above v1.x.x (except `luxfi/lattice/v7` and `luxfi/zapdb/v4` which are already >v1)
 5. Go version must be **1.26.1** or higher

apps/docs/content/docs/reference/lux-standard.mdx

@@ -61,7 +61,7 @@ Lux Standard is the canonical contract library for building on Lux C-Chain and L
 - Remapping: `@luxfi/contracts/=contracts/` in foundry.toml
 - FHE contracts require T-Chain (ThresholdVM) -- will not work on plain C-Chain
 - Post-quantum precompiles (ML-DSA, FROST, etc.) require Lux-specific EVM precompile addresses
-- Never use EWOQ keys
+- Never use well-known test keys -- derive keys from `LUX_MNEMONIC`
 - Private keys via `.env` file (never committed), loaded via `dotenv`
 
 ## Quick reference