FHEVM Files

v0.14.0 is a protocol and operations release focused on KMS context/epoch rotation, unified user decryption, confidential bridging, and safer coprocessor rollout and migration paths.

Highlights

• Completed the KMS context/epoch lifecycle for protocol upgrades and key rotation. Host contracts, KMS connector, relayer, SDK, and test tooling understand context-aware extraData, epoch validation, and KMS context switching. This release adds epoch destruction (destroyKmsEpoch), single-in-flight enforcement for lifecycle operations, signature-checked epoch activation confirmations, and getters for context-switch monitoring.
• Shipped unified EIP-712 user decryption. Self and delegated decryption share one request model, with per-handle ownership, durationSeconds, protocol-versioned permits, ERC-1271 smart-account signatures, and context-ID validation on the unified path.
• Added confidential bridging for encrypted handles through the LayerZero-based ConfidentialBridge, bridge events, Solidity helper APIs, deploy/prepareUpgrade tasks for existing chains, a wiring runbook, LZ-delegate auto-resync to the ACL owner, post-upgrade endpoint verification, and end-to-end bridge tests.
• Expanded Solidity developer APIs: FHE.toExternal(...) for all encrypted types and FHE.mulDiv(...) for widened multiply/divide, with HCU accounting including the scalar-type check for fheMulDiv.
• Hardened gateway and decryption validation: context-aware decryption consensus, v2 extraData with epoch ID, stricter handle/context checks, per-context KMS threshold setters with caps on threshold and signer set, and clearer handling of invalid KMS signer vs. transaction-sender mismatch.
• Improved coprocessor reliability for migration and live operations: host-listener consumer/catchup paths and full block payloads with adaptive Redis drain, SNS/S3 ciphertext migration (helm charts, dedicated concurrency and DB pool, stalled-error backoff), block-context materialization groundwork with a wave1 migration verification script, --seed-start-block for the host-listener poller, stalled dependency-chain parking, replay of quorum-accepted input proofs, drift-recovery hardening with documented quorum requirements, fatal DB-loss restart behavior, and latency/gap metrics.
• Added ciphertext attestation plumbing and shadow verification in the KMS connector, including the shared ciphertext-attestation crate, embedded ciphertext format, coprocessor registry refresh, and S3 material verification.
• Improved SDK compatibility across protocol versions and runtimes: automatic protocol/WASM version resolution, bundled TFHE, Next.js/Turbopack fixes, more robust WASM loading, cleartext mode, multi-version host-contracts support, better relayer error surfacing, and a narrower public API surface.
• Strengthened rollout and release tooling: stateful rollout runbooks, KMS generation/context-switch and abort-keygen/abort-CRS-gen commands, multi-KMS threshold scenarios, multi-chain and multichain-isolation test coverage, generic host-chain support in the kms-worker chart, and CI/Helm hardening for release branches.
• Security and dependency maintenance: tfhe-rs 1.6.1 → 1.6.3 (tfhe-versionable 0.8.0, tfhe-zk-pok 0.8.2), zk-verifier attack-surface reduction, and fixes for RUSTSEC-2026-0185, -0204, and -0220.

Breaking / upgrade notes

• SDK decryption permits moved to the unified signDecryptionPermit() API. durationDays is replaced by durationSeconds, permit objects carry a protocol version, and several low-level SDK exports were removed in favor of high-level encrypt/decrypt/sign actions.
• User-decryption authorization moves to the unified v2 flow: contract allowlist and signature checks are handled by the KMS connector for the new path; legacy on-chain request shapes remain only for the deprecation window.
• Host/gateway contracts receive new reinitializer versions (including FHEVMExecutor, HCULimit, and ProtocolConfig) and protocol storage for KMS epochs, context anchors, decryption invalidation, and confidential bridge configuration.
• The KMSGeneration Gateway migration path was removed. Deployment and rollout flows must use the new migration/verification/context-switch tooling (deployProtocolConfigFromMigration, deployKMSGenerationFromMigration, upgradeKMSGeneration, verify tasks, and the KMS/wave1 migration verification scripts).
• The coprocessor's Ethereum chain-ID flag was renamed to the canonical protocol-config chain ID; host_chains seeding is now declarative. Update coprocessor configuration accordingly.