Homomorphic Encryption
Readiness
TRL 5 · SRL 5 · gap 0
Gap = technical readiness − societal readiness. Positive: the technology is ready and society is not. Negative: society wants it more than the technology can deliver.
Not scored. Watchlist entries do not enter any gradient.
Homomorphic encryption lets a computer perform useful work on data it cannot read. The data goes in encrypted, the computation runs on the ciphertext, and the result decrypts correctly at the other end — so a party can process information without ever holding it.
If that sounds like it dissolves a large class of privacy trade-offs, it does. A hospital could run analysis on another hospital's records. A government could query a dataset it is not permitted to see. The technique is proven and the mathematics is not in doubt.
The constraint is cost. Fully homomorphic operations run orders of magnitude slower than the same computation in the clear, and that overhead has fallen without collapsing. So the deployments are the ones where the privacy is worth the arithmetic — narrow, high-value, usually regulated — and the general case is still waiting on hardware acceleration.
Common misconception: that it is not ready. It is ready, and expensive, which is a different problem with a different solution.
What it does
mechanism — not yet written. Published as missing rather than hidden.
Candidate megatrends — unreviewed
- Automation of Cognitive Work
- Digital Sovereignty
- Synthetic Media and the Verification Collapse
- The Application Gap