fhEVM
v0.14.5 open-sourceThe section your link pointed to isn't on fhEVM's page any more, so we've brought you to the top.
FHEVM, a full-stack framework for integrating Fully Homomorphic Encryption (FHE) with blockchain applications
euint64 result = FHE.mulDiv(encryptedA, encryptedB, encryptedDivisor);
externalEuint64 ext = FHE.toExternal(encryptedValue);
const permit = await signDecryptionPermit({ handles: [handle], durationSeconds: 3600, signer });
host-listener --seed-start-block=12345678
// import "@fhevm/lib-solidity/config/polygon-amoy.sol";
gateway listen --ciphertext-commits-address <checksum_address>
coprocessor host-listener --only-catchup-loop
bool isValid = FHE.checkSignatures(fheVal, publicKey);
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
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
Website history
zama.org, every changeZama'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 → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
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.
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
Other 1
Nothing first seen in this window. That doesn't mean fhEVM shipped nothing, only that we found no record of it.
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
24 entries
No entries match these filters.
- October 20263
- September 20262
- August 20261
- July 20262
- June 20261
- April 20261
- February 20261
- January 20261
- December 20252
- November 20253
- October 20254
- September 20251
- July 20251
- June 20251
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.
- Contributors 53 −1 vs prior 12 months
- Maintainers 15 +13 joined · −13 left, last 12 months
- Bus factor 7 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 2 days first maintainer reply 41 hours
- Open backlog 29 of 105 issues ever filed
- Issues opened / month 3 · 0 communitymaintainers
- Open backlog 29
- Contributors / month 20
- Commits / month 126
- Stars 24,815
- 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.