mirror of
https://github.com/luxfhe/torus.git
synced 2026-10-30 17:07:26 +00:00
zeekay
27f6f8d258
Sweep of the upstream-Concrete fork applying the canonical Lux FHE
naming map:
zama-ai/concrete-ml → luxfhe/ml-sdk
zama-ai/concrete → luxfhe/torus
zama-ai → luxfhe
github.com/zama-ai → github.com/luxfhe
docs.zama.ai → docs.luxfhe.com
zama-pypi-cpu/gpu → luxfhe-pypi-cpu/gpu
Concrete ML → TorusML
concrete-ml → torus-ml
concrete_ml → torus_ml
Concrete by Zama → Torus by Lux Industries
Concrete framework → Torus framework
Concrete compiler → Torus compiler
tfhe-rs / TFHE-rs → Lux-FHE
fhEVM → TorusEVM
Zama Concrete (ML) → Lux Torus(ML)
Zama → Lux Industries
Fhenix → (removed)
Files renamed for consistency:
ci/scripts/test_cml.sh → test_torus_ml.sh
tools/torus-protocol/src/concrete-protocol.capnp → torus-protocol.capnp
docker/Dockerfile.concrete-compiler-env → Dockerfile.torus-compiler-env
setup.py:
author="Zama Team" → author="Lux Industries"
The 11 files that still contain "Zama" string matches are upstream
license-attribution headers that BSD-3-Clause-Clear §1-§2 REQUIRES
us to retain verbatim. These are:
README.md (legal compliance disclosure)
.github/workflows/scripts/check_for_license.sh (validates upstream headers)
compilers/torus-compiler/compiler/lib/Bindings/Python/torus/ (9 files,
"Part of the Concrete Compiler Project, under the BSD3 License
with Zama Exceptions." copyright-notice headers)
Per §3, no "Zama" name is used to endorse or promote Torus — every
product-facing surface is rebranded; only the legally-required
license headers retain the upstream copyright.
Verified: 0 non-attribution "Zama" content references, 0 "Concrete ML"
content references, 0 "fhEVM" content references. The single binary
mlbench.zip retains an embedded "concrete-ml" string inside the
archive (benign, not a brand reference).