PAGES
← all tools
◆ Data Security & DLP

fhEVM

v0.14.5 open-source

FHEVM, a full-stack framework for integrating Fully Homomorphic Encryption (FHE) with blockchain applications

Summary

fhEVM is an open-source framework that enables confidential smart contracts on EVM-compatible blockchains by leveraging Fully Homomorphic Encryption (FHE), and it is released under the BSD-3-Clause license. It operates as a library that developers import into their own code and is intended for application developers working in the data-security space. The documentation places it alongside concepts like Zama Confidential Blockchain Protocol, and the project has seen four releases within the tracked timeframe, with the most recent one published this week.

FHEVM, a full-stack framework for integrating Fully Homomorphic Encryption (FHE) with blockchain applications

How fhEVM helps

Which parts of my contract's state can stay hidden from everyone but the parties I choose?

encrypted types in Solidity let state and transaction data stay ciphertext end-to-end onchain, so values are processed under encryption rather than exposed to validators or observers

Can I let a value leave my confidential contract without breaking its encryption?

converts any encrypted value to an external representation so it can be consumed off-chain or passed to another system while remaining ciphertext until an authorized party decrypts it

How do I let a specific user decrypt just the values they're entitled to see?

issues a signed decryption permit scoped to individual handles with an explicit duration, so authorization is per-value and expires rather than granting blanket access

Can my confidential contract's encrypted values move to another chain without being exposed in transit?

bridges encrypted handles across chains through a dedicated cross-chain bridge, carrying the ciphertext and its access-control state along rather than decrypting at the boundary

Will upgrading to a newer release silently break my existing deployment or decryption flow?

flags removed migration paths and renamed configuration fields explicitly, so a deployment still pointed at the old KMS generation path or the old chain-ID flag surfaces as an incompatibility instead of failing silently

Are my encrypted computations still correct as values get combined in more complex operations?

tracks homomorphic capacity unit accounting per operation, including widened arithmetic like multiply-divide, so cost and correctness bounds on chained encrypted operations are visible before deployment

all 27 features, with the evidence for each →

Languages

Not documented

Features

27 capabilities · 2 backed by code, an API document or a real run

Built from fhEVM's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • fhEVM covers 1 of the 8 data discovery and protection capabilities we track.

What fhEVM offers you

  • Client SDKs4
  • Command-line interface4
  • S3 export1
All capabilities 27 capabilities
KMS threshold and epoch lifecycle management shipped Provides per-context KMS threshold setters with caps on threshold and signer set, epoch creation and destruction, single-in-flight enforcement, and signature-checked activation confirmations for hardened decryption consensus. 9 releases · 2 other sources · first seen Sep 2025

Shared capability: Encryption at rest

release 9 total

  • Adds per-context KMS threshold setters with caps on threshold and signer set for hardened decryption consensus. v0.14.0 · Aug 2026 · source · release history
  • destroyKmsEpoch for explicit KMS context destruction and lifecycle management v0.14.0 · Aug 2026 · source · release history
  • Adds destroyKmsEpoch to the KMS connector for epoch destruction as part of the KMS context/epoch lifecycle, alongside single-in-flight enforcement, signature-checked epoch activation confirmations, and getters for context-switch monitoring. v0.14.0 · Aug 2026 · source · release history
  • Adds --ciphertext-commits-address flag to the gateway listener for opt-in ciphertext drift detection via local digest comparison against on-chain consensus v0.12.0 · Apr 2026 · source · release history
  • Adds a new Operator Staking system using ERC4626-based contracts, including reward distribution logic. v0.11.0 · Feb 2026 · source · release history
  • Adds a non-blocking, distributed locking mechanism in tfhe-worker. v0.10.5 · Dec 2025 · source · release history

example

  • Rotate KMS epochs and destroy the old context once it is no longer needed. await kmsConnector.destroyKmsEpoch(epochId); v0.14.0 · Aug 2026 · source
  • Enable ciphertext drift detection by comparing local digests against on-chain consensus during gateway startup gateway listen --ciphertext-commits-address <checksum_address> v0.12.0 · Apr 2026 · source
Confidential smart contract development framework shipped Provides a framework for writing and deploying FHE-powered confidential smart contracts on EVM-compatible blockchains. 8 releases · 1 other source · first seen Oct 2025

Also counts toward: Client SDKs

release 8 total

  • Add BSC testnet chain support to the SDK with the new feat(sdk): add BSC testnet chain backport, enabling encrypted smart contract development on Binance Smart Chain testnet.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v0.14.5 · Oct 2026 · source · release history
  • Transient allowance for inputs to sender has been removed from the Solidity library (library-solidity); contracts relying on this allowance behaviour will no longer work as before. v0.14.5 · Oct 2026 · source · release history
  • Remove transient allowance for inputs to sender in the Solidity library, changing how input permissions are granted on-chain. v0.14.5 · Oct 2026 · source · release history
  • Improves scalar operand handling in host-contracts for FHE arithmetic operations. v0.14.2 · Oct 2026 · source · release history
  • Adds BNB to the supported chainIds in host-contracts, enabling FHE workflows on the BNB chain.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v0.14.2 · Oct 2026 · source · release history
  • Adds automatic protocol/WASM version resolution and bundled TFHE to the SDK, with cleartext mode, multi-version host-contracts support, and a narrower public API surface. v0.14.0 · Aug 2026 · source · release history

docs

  • Framework for building confidential smart contracts on EVM-compatible blockchains using Fully Homomorphic Encryption (FHE).
Coprocessor block processing and replay shipped Processes full block payloads with adaptive Redis drain, stalled dependency-chain parking, quorum-accepted input proof replay, and drift-recovery hardening to support migration and live-operation reliability. 7 releases · 1 other source · first seen Jun 2025

release 7 total

  • Adds replay of quorum-accepted input proofs and drift-recovery hardening with documented quorum requirements to the coprocessor. v0.14.0 · Aug 2026 · source · release history
  • Adds full block payloads with adaptive Redis drain and stalled dependency-chain parking to the coprocessor for improved migration and live-operation reliability. v0.14.0 · Aug 2026 · source · release history
  • Adds --seed-start-block flag to the host-listener poller to allow specifying a starting block for seeding operations v0.13.2 · Jul 2026 · source · release history
  • gpu acceleration is available for ZK proof verification, Switch-and-Squash (SnS), and re-randomisation in the coprocessor. v0.11.0 · Feb 2026 · source · release history
  • New host-listener poller mode provides an alternative to WebSocket-based event listening for the coprocessor scheduler. v0.11.0 · Feb 2026 · source · release history
  • Coprocessor host-listener gains a new --only-catchup-loop flag to run exclusively in catch-up mode. v0.10.2 · Dec 2025 · source · release history

example

  • Start the host-listener poller from a specific block height instead of genesis. host-listener --seed-start-block=12345678 v0.13.2 · Jul 2026 · source
Coprocessor observability and configuration shipped Exposes latency and gap metrics for block-processing performance and provides flags for controlling block replay start point and slow-lane assignment for dependent operation chains. 6 releases · first seen Oct 2025

Also counts toward: Command-line interface

release

  • Generates e2e coprocessor configuration from environment variables in the test suite, enabling automated and CI-friendly stack setup.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v0.14.3 · Oct 2026 · source · release history
  • Adds --seed-start-block flag to the host-listener poller for controlling coprocessor block replay start point. v0.14.0 · Aug 2026 · source · release history
  • Adds latency/gap metrics to the coprocessor for observability of block-processing performance. v0.14.0 · Aug 2026 · source · release history
  • Adds reliability metrics to the coprocessor host-consumer component v0.13.1 · Jul 2026 · source · release history
  • Exposes new metrics for the gw-listener component in the coprocessor to support observability. v0.9.6 · Nov 2025 · source · release history
  • gw-listener accepts bucket.domain URLs for object storage integration. v0.9.1 · Oct 2025 · source · release history
Multi-chain SDK support shipped Adds chain configurations — including Polygon mainnet — to the SDK and Solidity library, with backported CLI support for stable release lines. 4 releases · 2 other sources · first seen Jul 2026

Also counts toward: Command-line interface, Client SDKs

release

  • Adds polygon CLI commands to the JavaScript SDK for cross-chain interactions v0.13.4 · Sep 2026 · source · release history
  • Backports the Polygon CLI to the 0.13.x release line, enabling Polygon-targeted workflows on the stable branch. v0.13.4 · Sep 2026 · source · release history
  • Adds Polygon mainnet chain configuration to the SDK and Solidity library. v0.14.1 · Sep 2026 · source · release history
  • Adds support for Polygon Amoy testnet via new chain configuration in library-solidity v0.13.2 · Jul 2026 · source · release history

example

  • Use the new CLI to interact with Polygon network from within the SDK environment. fhevm polygon --network mainnet v0.13.4 · Sep 2026 · source
  • Reference the Polygon Amoy testnet configuration in your Solidity project. // import "@fhevm/lib-solidity/config/polygon-amoy.sol"; v0.13.2 · Jul 2026 · source
Unified EIP-712 user decryption permits shipped suggested Issues and validates EIP-712 decryption permits via signDecryptionPermit(), merging self and delegated decryption into a single per-handle, duration-in-seconds model with ERC-1271 smart-account support. 6 releases · first seen Jun 2025

Suggested capability: Data access governance. This is our guess, not confirmed.

release

  • SDK permits moved to signDecryptionPermit(); durationDays replaced by durationSeconds and low-level SDK exports removed v0.14.0 · Aug 2026 · source · release history
  • Unified EIP-712 signDecryptionPermit() API for self and delegated decryption with durationSeconds v0.14.0 · Aug 2026 · source · release history
  • Ships unified EIP-712 user decryption via signDecryptionPermit(), merging self and delegated decryption into one request model with per-handle ownership, durationSeconds, protocol-versioned permits, and ERC-1271 smart-account signature support. v0.14.0 · Aug 2026 · source · release history
  • The signDecryptionPermit() API is now the required SDK decryption permit path; 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. v0.14.0 · Aug 2026 · source · release history
  • Introduces a new codegen feature that replaces the previous requestDecryption method v0.9.10 · Nov 2025 · source · release history
  • Adds FHE.requestDecryption with msg.value support, replacing deprecated GatewayCaller v0.7.0 · Jun 2025 · source · release history
FHE encrypted integer operations shipped Exposes FHE arithmetic operations on encrypted integers in Solidity, including a widened multiply-divide operation via FHE.mulDiv(). 4 releases · 1 other source · first seen Jun 2026

release

  • Improves scalar operand handling logic in host-contracts v0.14.2 · Oct 2026 · source · release history
  • FHE.toExternal(...) and FHE.mulDiv(...) Solidity functions for encrypted types and widened arithmetic v0.14.0 · Aug 2026 · source · release history
  • Adds FHE.mulDiv(...) for widened multiply-divide operations on encrypted integers, with HCU accounting including the scalar-type check for fheMulDiv. v0.14.0 · Aug 2026 · source · release history
  • Adds ACL deny list support in host-contracts to block specific accounts from persisting FHE handles. v0.13.0 · Jun 2026 · source · release history

example

  • Call the new widened multiply-divide operation on encrypted integers inside a confidential Solidity contract. euint64 result = FHE.mulDiv(encryptedA, encryptedB, encryptedDivisor); v0.14.0 · Aug 2026 · source
Coprocessor chain-ID and host-chain configuration shipped Aligns the coprocessor's Ethereum chain-ID flag to the canonical protocol-config chain ID and moves host_chains seeding to a declarative configuration model. 3 releases · first seen Aug 2026

release

  • Adds bnb to the supported chainIds in host-contracts configuration v0.14.2 · Oct 2026 · source · release history
  • The coprocessor's Ethereum chain-ID flag was renamed to the canonical protocol-config chain ID; host_chains seeding is now declarative — coprocessor configuration must be updated accordingly. v0.14.0 · Aug 2026 · source · release history
  • Coprocessor Ethereum chain-ID flag renamed to protocol-config chain ID v0.14.0 · Aug 2026 · source · release history
User decryption request handling shipped Processes user decryption requests and returns all shares per request, with authorization managed through the unified v2 decryption flow. 2 releases · 1 other source · first seen Aug 2026

release

  • Relayer now returns all user-decrypt shares per request, rather than a subset. v0.13.4 · Sep 2026 · source · release history
  • User-decryption authorization moves to the unified v2 flow; legacy on-chain request shapes remain only for the deprecation window. v0.14.0 · Aug 2026 · source · release history

example

  • Ensure your relayer integration handles the full list of shares for decryption verification. const shares = await relayer.getDecryptionShares(txHash); if (shares.length === expectedCount) { /* process */ } v0.13.4 · Sep 2026 · source
Ciphertext attestation and shadow verification shipped suggested Adds ciphertext attestation plumbing and shadow verification in the KMS connector, including a shared attestation crate, embedded ciphertext format, coprocessor registry refresh, and S3 material verification. 2 releases · 1 other source · first seen Nov 2025

Suggested capability: Encryption at rest. This is our guess, not confirmed.

release

  • Ciphertext attestation plumbing in the KMS connector, including shared ciphertext-attestation crate v0.14.0 · Aug 2026 · source · release history
  • Adds ciphertext attestation plumbing and shadow verification in the KMS connector, including a shared ciphertext-attestation crate, embedded ciphertext format, coprocessor registry refresh, and S3 material verification. v0.14.0 · Aug 2026 · source · release history

example

  • Verify the signature of an encrypted value before using it in a computation. bool isValid = FHE.checkSignatures(fheVal, publicKey); v0.9.13 · Nov 2025 · source
Encrypted value external conversion shipped Converts any encrypted value to an external representation for off-chain consumption or cross-chain bridging via FHE.toExternal(). 2 releases · 1 other source · first seen Aug 2026

release

  • FHE.toExternal(...) and FHE.mulDiv(...) Solidity functions for encrypted types and widened arithmetic v0.14.0 · Aug 2026 · source · release history
  • Adds FHE.toExternal(...) for all encrypted types, enabling conversion of any encrypted value to an external representation from Solidity. v0.14.0 · Aug 2026 · source · release history

example

  • Convert any encrypted value to an external representation for off-chain consumption or bridging. externalEuint64 ext = FHE.toExternal(encryptedValue); v0.14.0 · Aug 2026 · source
Protocol and KMS deployment and migration tooling shipped Provides Hardhat tasks — deployProtocolConfigFromMigration, deployKMSGenerationFromMigration, upgradeKMSGeneration, and verify — as the required deployment and rollout path, replacing the removed KMSGeneration Gateway migration path. 3 releases · first seen Aug 2026

Also counts toward: Command-line interface

release

  • The KMSGeneration Gateway migration path was removed; deployment and rollout flows must use deployProtocolConfigFromMigration, deployKMSGenerationFromMigration, upgradeKMSGeneration, verify tasks, and the KMS/wave1 migration verification scripts. v0.14.0 · Aug 2026 · source · release history
  • Adds deployProtocolConfigFromMigration, deployKMSGenerationFromMigration, upgradeKMSGeneration, and verify Hardhat tasks as the new required deployment and rollout path replacing the removed KMSGeneration Gateway migration path. v0.14.0 · Aug 2026 · source · release history
  • KMSGeneration Gateway migration path removed; deployment must use deployProtocolConfigFromMigration, deployKMSGenerationFromMigration, upgradeKMSGeneration, and verification tasks v0.14.0 · Aug 2026 · source · release history
KMS context and epoch replication to replica chains shipped Mirrors the canonical KMS context and epoch onto replica chains via dedicated host-contract tasks. 2 releases · first seen Sep 2026

Also counts toward: Command-line interface

release

  • Adds tasks to mirror the canonical KMS context and epoch onto replica chains in host contracts. v0.14.1 · Sep 2026 · source · release history
  • Adds mirror-kms-context and mirror-epoch hardhat tasks to replicate the canonical KMS context and epoch onto replica nodes v0.14.1 · Sep 2026 · source · release history
Confidential cross-chain bridge shipped Bridges encrypted handles across chains using the LayerZero-based ConfidentialBridge, with bridge events, Solidity helper APIs, deploy/upgrade tasks, and LZ-delegate auto-resync. 2 releases · first seen Aug 2026

release

  • Confidential bridging via LayerZero-based ConfidentialBridge contract and Solidity helper APIs v0.14.0 · Aug 2026 · source · release history
  • Adds the ConfidentialBridge (LayerZero-based) for encrypted handle bridging across chains, including bridge events, Solidity helper APIs, deploy/prepareUpgrade tasks, LZ-delegate auto-resync to the ACL owner, and post-upgrade endpoint verification. v0.14.0 · Aug 2026 · source · release history
SDK automatic protocol and WASM version resolution shipped Resolves protocol and WASM versions automatically, bundles TFHE, supports cleartext mode and multi-version host contracts, and narrows the public API surface to high-level encrypt/decrypt/sign actions. 2 releases · first seen Aug 2026

Also counts toward: Client SDKs

release

  • Adds automatic protocol/WASM version resolution and bundled TFHE to the SDK, with cleartext mode, multi-version host-contracts support, and a narrower public API surface. v0.14.0 · Aug 2026 · source · release history
  • The signDecryptionPermit() API is now the required SDK decryption permit path; 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. v0.14.0 · Aug 2026 · source · release history
Unified decryption permit request via SDK shipped suggested Issues a unified EIP-712 decryption permit from the SDK using the per-handle, duration-in-seconds model. 2 other sources · first seen Aug 2026

Suggested capability: Data access governance. This is our guess, not confirmed.

Also counts toward: Client SDKs

example

  • Request a unified EIP-712 decryption permit from the SDK with the new per-handle, duration-in-seconds model. const permit = await signDecryptionPermit({ handles: [handle], durationSeconds: 3600, signer }); v0.14.0 · Aug 2026 · source
  • Request decryption with the new unified permit using seconds duration in a Next.js frontend. const permit = await wallet.signDecryptionPermit(handle, { durationSeconds: 3600, protocolVersion: 'v2' }); v0.14.0 · Aug 2026 · source
PRSS initialization and key resharing shipped Adds flows for Private Random Shared Secret (PRSS) initialization and key resharing within the same operator set. 2 releases · first seen Nov 2025

release

  • Adds PRSSInit and KeyReshareSameSet flows for threshold key share regeneration. v0.13.0 · Jun 2026 · source · release history
  • Adds PRSSInit and KeyReshareSameSet flows to handle private random shared secret initialization and key resharing within the same set. v0.9.6 · Nov 2025 · source · release history
Ciphertext drift detection shipped Detects inconsistencies in local ciphertext state by comparing digests against on-chain consensus during gateway startup. 1 release · 1 other source · first seen Apr 2026

release

  • Adds --ciphertext-commits-address flag to the gateway listener for opt-in ciphertext drift detection via local digest comparison against on-chain consensus v0.12.0 · Apr 2026 · source · release history

example

  • Enable ciphertext drift detection by comparing local digests against on-chain consensus during gateway startup gateway listen --ciphertext-commits-address <checksum_address> v0.12.0 · Apr 2026 · source
SDK relayer selection shipped Exposes a relayer query option in the SDK, giving developers control over which relayer is used when submitting encrypted transactions. 1 release · first seen Oct 2026

release

  • Add a relayer query option to the SDK via the backported relayer query option (#4544), giving developers control over relayer selection when submitting encrypted transactions. v0.14.5 · Oct 2026 · source · release history
Coprocessor ciphertext migration shipped Migrates ciphertexts via SNS/S3 with dedicated concurrency and DB pool controls, stalled-error backoff, and a wave1 migration verification script. 1 release · first seen Aug 2026

Also counts toward: S3 export

release

  • Adds SNS/S3 ciphertext migration support with dedicated concurrency and DB pool controls, stalled-error backoff, and a wave1 migration verification script. v0.14.0 · Aug 2026 · source · release history
Host and gateway contract reinitializer and storage upgrades shipped Adds new reinitializer versions for FHEVMExecutor, HCULimit, and ProtocolConfig contracts, introducing protocol storage for KMS epochs, context anchors, decryption invalidation, and confidential bridge configuration. 1 release · first seen Aug 2026

release

  • Adds new reinitializer versions for FHEVMExecutor, HCULimit, and ProtocolConfig host/gateway contracts with protocol storage for KMS epochs, context anchors, decryption invalidation, and confidential bridge configuration. v0.14.0 · Aug 2026 · source · release history
Project-scoped CLI operations verified Scopes CLI check and update binding operations to a specified project via the --project flag. 1 other source · first seen May 2026

command line

  • --project — The project to check or update bindings for. v0.11.4 · May 2026 · command-line history
Slow-lane scheduling for dependent operation chains verified Enables slow-lane assignment for dependent operation chains in the coprocessor via the --dependent-ops-max-per-chain flag, with 0 disabling the feature. 1 other source · first seen May 2026

command line

  • --dependent-ops-max-per-chain — enables slow-lane assignment (`0` disables). v0.12.5 · May 2026 · command-line history
Homomorphic Compute Unit (HCU) limits and whitelisting shipped Enforces configurable per-block, per-transaction, and per-depth computational cost limits with whitelist support for privileged callers. 1 release · first seen Apr 2026

release

  • Adds HCULimit contract with configurable per-block, per-transaction, and per-transaction-depth Homomorphic Compute Unit limits and a whitelist mechanism for privileged callers v0.12.0 · Apr 2026 · source · release history
Confidential token management shipped suggested Provides registry contracts and upgradeable wrappers for managing confidential tokens on-chain. 1 release · first seen Feb 2026

Suggested capability: Data tokenization. This is our guess, not confirmed.

release

  • Introduces Confidential Tokens Registry and ERC7984 upgradeable wrapper contracts for token management. v0.11.0 · Feb 2026 · source · release history
Confidential token registry support shipped suggested Provides specific support for Confidential Tokens Registry via ERC7984 upgradeable wrapper contracts. 1 release · first seen Feb 2026

Suggested capability: Data tokenization. This is our guess, not confirmed.

release

  • Introduces Confidential Tokens Registry and ERC7984 upgradeable wrapper contracts for token management. v0.11.0 · Feb 2026 · source · release history
Operator staking and reward distribution shipped Enables staking of operators via ERC4626 contracts with automated reward distribution logic. 1 release · first seen Feb 2026

release

  • Adds a new Operator Staking system using ERC4626-based contracts, including reward distribution logic. v0.11.0 · Feb 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for fhEVM, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail fhEVM puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Website history

zama.org, every change

Zama's home page and 22 more pages as they looked each month from October 2025 to October 2026: 26 renders, 2 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Coverage

Missing something? Tell us

What fhEVM connects to, runs on and detects, read from its release notes and docs. So far: 1 new supported platform.

Show

1 change, tracked since Oct 30, 2026.

  • Oct 302026

    new BSC testnet support in library-solidity and SDK

    feat(library-solidity): add BSC testnet config by @0xalexbel in https://github.com/zama-ai/fhevm/pull/4714 * feat(sdk): add BSC testnet chain by @0xalexbel in https://github.com/zama-ai/fhevm/pull/4723

    v0.14.5 Source ↗

How we count

Read from 3 of 24 release notes and docs updates we hold for fhEVM. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through fhEVM's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

24 entries

  1. October 20263
  2. September 20262
  3. August 20261
  4. July 20262
  5. June 20261
  6. April 20261
  7. February 20261
  8. January 20261
  9. December 20252
  10. November 20253
  11. October 20254
  12. September 20251
  13. July 20251
  14. June 20251
    Show
    Coverage in all entries

    24 entries

    Project health

    Issue, contributor and maintainer activity in zama-ai/fhevm, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 53 −1 vs prior 12 months
    2. Maintainers 15 +13 joined · −13 left, last 12 months
    3. Bus factor 7 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 2 days first maintainer reply 41 hours
    6. Open backlog 29 of 105 issues ever filed
    1. Issues opened / month 3 · 0 communitymaintainers
    2. Open backlog 29
    3. Contributors / month 20
    4. Commits / month 126
    5. Stars 24,815
    Issue themes, last 12 months
    • features 1%
    • docs 32%
    • other 67%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →