chore: sync working tree

Commits 1 outstanding change(s) that were sitting uncommitted.
No build artifacts and no secrets in the changeset (both checked).
This commit is contained in:
zeekay
2026-07-26 10:01:41 -07:00
parent e5a565da4d
commit 587a4d0eb9
+2 -2
View File
@@ -15,7 +15,7 @@ of those chains run latency-sensitive cryptography on the hot path:
- K-Chain (keyvm) — ML-KEM/ML-DSA on cross-chain hot path
- Z-Chain (zkvm) — Groth16 verification, Poseidon hashing
- B-Chain (bridgevm) — ECDSA batch verification of MPC signatures
- T-Chain (thresholdvm) — FHE bootstrapping
- T-Chain (mpcvm) — FHE bootstrapping
- Q-Chain (quantumvm) — Dilithium signing/verification
Sharing one global session means:
@@ -113,7 +113,7 @@ calls observe `ErrSessionClosed` on the next iteration.
- One process-wide session, lazily initialized
- Shared, no isolation, no priority, no budget
- All existing callers (`evmgpu`, `zkvm`, `bridgevm`, `quantumvm`,
`thresholdvm`, `cevm`) keep working without changes
`mpcvm`, `cevm`) keep working without changes
New code should use `NewVMSession` per VM. Migrate legacy callers when their
ops list grows large enough to compete for GPU time with another VM.