chore: sync working tree

Commits 2 outstanding change(s) that were sitting uncommitted.
No build artifacts and no secrets in the changeset (both checked).

LLM.md

@@ -35,7 +35,24 @@ domain-execution chain that MUST consume UTXO settlement via the
 | `aivm/` | **A** | Inference receipt + attestation. Rides B's settlement engine (LP-0130 §9) | LP-5000 |
 | `bridgevm/` | **B** | Cross-chain message lifecycle. Fees deducted from bridged amount (LP-0130 §8) | LP-6000 |
 | `mpcvm/` | **M** | MPC signing / custody. Service fees paid by originating chain (LP-0130 §7); no user M-balance | LP-7100 |
-| `mpcvm/fhe/` | **F** | FHE runtime. Encrypted supply reconciles to X-escrow (LP-0130 §2, I-5) | LP-8200 |
+| `mpcvm/fhe/` | **F** | FHE runtime **library** — a package inside `mpcvm`, not a chain. See the deployment note below. | LP-8200 |
+
+**Deployment reality (probed on mainnet 96369, `platform.getBlockchains`).** Ten
+chains are live: P X + C D Q Z A B G K. **M and F are NOT deployed**, and the
+two are not equally close to shipping:
+
+- **M** has a full VM (`mpcvm/`, `mpcvm/cmd/plugin`) — it builds, it just has no
+  chain registered on any network.
+- **F** has **no VM at all**. `luxfi/constants` reserves
+  `FHEVMID = {'f','h','e','v','m'}` and `luxfi/node/node/vms.go` lists it in
+  `OptionalVMs` as plugin `fhevm`, so luxd scans `--plugin-dir` for a binary
+  that this repo never produces (no `fhevm/` directory ⇒ no `make` target ⇒ no
+  binary). `mpcvm/fhe/` above is the FHE runtime library, not a standalone
+  F-Chain. **F-Chain is a spec (LP-8200, LP-167) with no shipping VM.**
+
+T-Chain is gone entirely — LP-134 dissolves it with zero remainder (threshold
+signing → M, FHE → F, cross-chain messaging/teleport → B). There is no
+`teleportvm` here and no `teleportvm` VM ID in `luxfi/constants`.
 
 **Service VMs** (not canonical primary chains under LP-0130):
 

README.md

@@ -25,20 +25,37 @@ Or copy binaries to `~/.lux/plugins/<vmid>`.
 
 ## VMs
 
-| VM | Chain | Purpose |
-|----|-------|---------|
-| evm | C-Chain | EVM smart contracts |
-| dexvm | D-Chain | Decentralized exchange |
-| aivm | A-Chain | AI/ML inference |
-| bridgevm | B-Chain | Cross-chain bridge |
-| graphvm | G-Chain | GraphQL data layer |
-| identityvm | I-Chain | Decentralized identity |
-| keyvm | K-Chain | Key management |
-| oraclevm | O-Chain | Oracle/off-chain data |
-| quantumvm | Q-Chain | Post-quantum consensus signing (Pulsar) |
-| relayvm | R-Chain | Cross-chain relay |
-| servicenodevm | S-Chain | Service node registry |
-| teleportvm | T-Chain | Unified teleport (bridge + relay + oracle) |
-| mpcvm (MPC) | M-Chain | MPC ceremonies (CGGMP21, FROST, Pulsar-general) — bridge custody for external wallets |
-| mpcvm (FHE) | F-Chain | FHE compute + TFHE bootstrap-key generation (encrypted EVM) |
-| zkvm | Z-Chain | Groth16 over BLS12-381 (rolls N × ML-DSA-65 sigs into 192-byte proof) |
+One row per directory in this repo. `make` derives its target list from the
+directory listing, so a VM that has no directory here has no binary — the table
+below and `ls` can never disagree.
+
+**Live** means the VM has a chain registered on Lux mainnet 96369
+(`platform.getBlockchains`).
+
+| VM | Chain | Live on 96369 | Purpose |
+|----|-------|---------------|---------|
+| evm | C-Chain | ✅ | EVM smart contracts |
+| dexvm | D-Chain | ✅ | Decentralized exchange |
+| aivm | A-Chain | ✅ | AI/ML inference |
+| bridgevm | B-Chain | ✅ | Cross-chain bridge — also owns *all* cross-chain messaging / relay / teleport (LP-6000); there is no separate `teleportvm` |
+| graphvm | G-Chain | ✅ | GraphQL data layer |
+| keyvm | K-Chain | ✅ | Key management |
+| quantumvm | Q-Chain | ✅ | Post-quantum consensus signing (Pulsar) |
+| zkvm | Z-Chain | ✅ | Groth16 over BLS12-381 (rolls N × ML-DSA-65 sigs into 192-byte proof) |
+| identityvm | I-Chain | ❌ built, not deployed | Decentralized identity |
+| oraclevm | O-Chain | ❌ built, not deployed | Oracle/off-chain data |
+| relayvm | R-Chain | ❌ built, not deployed | Cross-chain relay |
+| mpcvm | M-Chain | ❌ built, not deployed | MPC ceremonies (CGGMP21, FROST, Pulsar-general) — bridge custody for external wallets (LP-7100) |
+| schain | S-Chain | ❌ built, not deployed | S3-style object storage (on-chain metadata / off-chain blob). Declares its own `VMID = ids.ID{'s','c','h','a','i','n'}` in `schain/factory.go` and is **not** in the canonical `luxfi/constants` VM-ID registry |
+
+`P-Chain` (platformvm) and `X-Chain` (xvm) are in-process core VMs registered by
+`luxfi/node`, not plugins built here. Together with the eight ✅ rows above they
+are the ten chains live on 96369.
+
+### Not in this repo
+
+| Name | Status |
+|------|--------|
+| `teleportvm` / T-Chain | **Removed.** LP-134 dissolves T-Chain with zero remainder: threshold signing → M-Chain, FHE → F-Chain, cross-chain messaging/teleport → B-Chain (`bridgevm`). LP-5013 and LP-7330 are deprecated by LP-134; see LP-7050 for the migration map. No `teleportvm` VM ID exists in `luxfi/constants`. |
+| `servicenodevm` | **Never existed.** The service-node registry was never built under this name; the S-Chain directory here is `schain/` and is object storage, not a registry. |
+| `fhevm` / F-Chain | **Unbuilt.** `luxfi/constants` reserves `FHEVMID = {'f','h','e','v','m'}` and `luxfi/node/node/vms.go` lists it in `OptionalVMs` as a plugin named `fhevm`, so luxd will scan `--plugin-dir` for it — but there is **no `fhevm/` directory in this repo and no plugin binary anywhere**, so that scan always comes up empty. The FHE *runtime library* lives at `mpcvm/fhe/`; it is a package inside `mpcvm`, not a standalone chain. F-Chain is a spec (LP-8200, LP-167) with no shipping VM. |