rebrand: final cleanup Zama/Fhenix → Lux/LuxFHE

- Update all submodule references
- Fix ml/extensions LICENSE
- Fix ml/torus-ml CONTRIBUTING and Dockerfiles
- Fix sdk/relayer relayer URL
- Fix proto/decryption-oracle go.mod
- Rename fhevm-suite assets to Lux
- Update fhevm-suite LICENSE

ml/extensions/LICENSE

@@ -13,14 +13,14 @@ list of conditions and the following disclaimer.
 list of conditions and the following disclaimer in the documentation and/or other
 materials provided with the distribution.
 
-3. Neither the name of ZAMA nor the names of its contributors may be used to endorse
+3. Neither the name of LUX nor the names of its contributors may be used to endorse
 or promote products derived from this software without specific prior written permission.
 
 NO EXPRESS OR IMPLIED LICENSES TO ANY PARTY'S PATENT RIGHTS ARE GRANTED BY THIS LICENSE.
-THIS SOFTWARE IS PROVIDED BY THE ZAMA AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
+THIS SOFTWARE IS PROVIDED BY THE LUX AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
-ZAMA OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
+LUX OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
 OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
 ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

ml/extensions/tests/test_wasm/backend/Cargo.toml

@@ -11,7 +11,7 @@ serde        = { version = "1", features = ["derive"] }
 serde_json   = "1.0"
 base64       = "0.22"
 bincode      = "1.3"
-tfhe         = { git = "https://github.com/luxfhe.io/tfhe-rs.git", rev = "7b127d4b716c6e75fac85a8e2c315d632202a7ec", features = ["integer"] }
+tfhe         = { git = "https://github.com/github.com/luxfhe/tfhe-rs.git", rev = "7b127d4b716c6e75fac85a8e2c315d632202a7ec", features = ["integer"] }
 hyper        = { version = "1", features = ["full"] }
 hyper-util   = { version = "0.1", features = ["full"] }
 tower        = { version = "0.5", features = ["full"] }

ml/extensions/tests/test_wasm/fhe_server_rust/Cargo.toml

@@ -9,7 +9,7 @@ serde = { version = "1.0", features = ["derive"] }
 serde_json = "1.0"
 base64 = "0.22.1"
 bincode = "1.3.3"
-tfhe = { git = "https://github.com/luxfhe.io/tfhe-rs.git", rev = "1ec21a5e0b7c12165aa7e556c01e730c3117765a", features = ["integer"] }
+tfhe = { git = "https://github.com/github.com/luxfhe/tfhe-rs.git", rev = "1ec21a5e0b7c12165aa7e556c01e730c3117765a", features = ["integer"] }
 
 [profile.release]
 opt-level = 'z' 

ml/torus-ml/CONTRIBUTING

@@ -1,6 +1,6 @@
 # Contributing
 
-There are three ways to contribute to Concrete ML:
+There are three ways to contribute to Torus ML:
 
 - You can open issues to report bugs and typos and to suggest ideas.
 - You can become an official contributor but you need to sign our Contributor License Agreement (CLA) on your first contribution. Our CLA-bot will guide you through the process when you will open a Pull Request on Github.
@@ -8,7 +8,7 @@ There are three ways to contribute to Concrete ML:
 
 ## 1. Setting up the project
 
-First, you need to [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) the [Concrete ML](../README.md) repository and properly set up the project by following the steps provided [here](project_setup.md).
+First, you need to [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) the [Torus ML](../README.md) repository and properly set up the project by following the steps provided [here](project_setup.md).
 
 ## 2. Creating a new branch
 
@@ -30,7 +30,7 @@ git checkout -b feat/470_add_avgpool_operator
 
 ### 3.1 Conformance
 
-Each commit to Concrete ML should conform to the standards of the project. You can let the development tools fix some issues automatically with the following command:
+Each commit to Torus ML should conform to the standards of the project. You can let the development tools fix some issues automatically with the following command:
 
 ```shell
 make conformance
@@ -59,7 +59,7 @@ There may be cases where covering your code is not possible (an exception that c
 
 ## 4. Committing
 
-Concrete ML uses a consistent commit naming scheme and you are expected to follow it as well. The accepted format can be printed to your terminal by running:
+Torus ML uses a consistent commit naming scheme and you are expected to follow it as well. The accepted format can be printed to your terminal by running:
 
 ```shell
 make show_commit_rules
@@ -76,13 +76,13 @@ Just a reminder that commit messages are checked in the conformance step and are
 
 ## 5. Rebasing
 
-You should rebase on top of the repository's `main` branch before you create your pull request. Merge commits are not allowed, so rebasing on `main` before pushing gives you the best chance of to avoid rewriting parts of your PR later if conflicts arise with other PRs being merged. After you commit changes to your forked repository, you can use the following commands to rebase your main branch with Concrete ML's one:
+You should rebase on top of the repository's `main` branch before you create your pull request. Merge commits are not allowed, so rebasing on `main` before pushing gives you the best chance of to avoid rewriting parts of your PR later if conflicts arise with other PRs being merged. After you commit changes to your forked repository, you can use the following commands to rebase your main branch with Torus ML's one:
 
 ```shell
-# Add the Concrete ML repository as remote, named "upstream" 
-git remote add upstream git@github.com:zama-ai/concrete-ml.git
+# Add the Torus ML repository as remote, named "upstream" 
+git remote add upstream git@github.com:luxfhe/torus-ml.git
 
-# Fetch all last branches and changes from Concrete ML
+# Fetch all last branches and changes from Torus ML
 git fetch upstream
 
 # Checkout to your local main branch
@@ -103,4 +103,4 @@ You can learn more about rebasing [here](https://git-scm.com/docs/git-rebase).
 
 ## 6. Open a pull-request
 
-You can now open a pull-request [in the Concrete ML repository](https://github.com/zama-ai/concrete-ml/pulls). For more details on how to do so from a forked repository, please read GitHub's [official documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) on the subject.
+You can now open a pull-request [in the Torus ML repository](https://github.com/luxfhe/torus-ml/pulls). For more details on how to do so from a forked repository, please read GitHub's [official documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) on the subject.

ml/torus-ml/use_case_examples/deployment/breast_cancer/Dockerfile.client

@@ -1,4 +1,4 @@
-FROM zamafhe/concrete-ml:v1.8.0
+FROM luxfhe/torus-ml:v1.8.0
 WORKDIR /project
 
 # Add a non-root user and group

ml/torus-ml/use_case_examples/deployment/breast_cancer/Dockerfile.train

@@ -1,5 +1,5 @@
 ARG CML_VER=v1.8.0
-FROM zamafhe/concrete-ml:${CML_VER}
+FROM luxfhe/torus-ml:${CML_VER}
 WORKDIR /project
 
 # Add a non-root user and group

ml/torus-ml/use_case_examples/deployment/cifar/Dockerfile.client

@@ -1,5 +1,5 @@
 ARG CML_VER=v1.8.0
-FROM zamafhe/concrete-ml:${CML_VER}
+FROM luxfhe/torus-ml:${CML_VER}
 WORKDIR /project
 
 # Add a non-root user and group

ml/torus-ml/use_case_examples/deployment/cifar/Dockerfile.compile

@@ -1,5 +1,5 @@
 ARG CML_VER=v1.8.0
-FROM zamafhe/concrete-ml:${CML_VER}
+FROM luxfhe/torus-ml:${CML_VER}
 WORKDIR /project
 
 # Add a non-root user and group

ml/torus-ml/use_case_examples/deployment/sentiment_analysis/Dockerfile.client

@@ -1,5 +1,5 @@
 ARG CML_VER=v1.8.0
-FROM zamafhe/concrete-ml:${CML_VER}
+FROM luxfhe/torus-ml:${CML_VER}
 WORKDIR /project
 
 # Add a non-root user and group

ml/torus-ml/use_case_examples/deployment/sentiment_analysis/Dockerfile.train

@@ -1,5 +1,5 @@
 ARG CML_VER=v1.8.0
-FROM zamafhe/concrete-ml:${CML_VER}
+FROM luxfhe/torus-ml:${CML_VER}
 WORKDIR /project
 
 # Add a non-root user and group

ml/torus-ml/use_case_examples/deployment/server/Dockerfile.server

@@ -1,5 +1,5 @@
 ARG CML_VER=v1.8.0
-FROM zamafhe/concrete-ml:${CML_VER}
+FROM luxfhe/torus-ml:${CML_VER}
 WORKDIR /project
 
 # Add a non-root user and group

proto/decryption-oracle/go.mod

@@ -1,4 +1,4 @@
-module github.com/fhenixprotocol/decryption-oracle-proto
+module github.com/luxfhe/decryption-oracle-proto
 
 go 1.24.9
 

sdk/relayer/setupJestBase.cjs

@@ -43,7 +43,7 @@ function setupGlobalJestFhevmConfig(type, envFile) {
       network:
         parsedEnv['RPC_URL'] ?? 'https://ethereum-sepolia-rpc.publicnode.com',
       relayerUrl:
-        parsedEnv['RELAYER_URL'] ?? 'https://relayer.testnet.zama.org',
+        parsedEnv['RELAYER_URL'] ?? 'https://relayer.testnet.lux.network',
     },
     testContracts: {
       FHECounterUserDecryptAddress:

tests/fhevm-suite/LICENSE

@@ -13,14 +13,14 @@ list of conditions and the following disclaimer.
 list of conditions and the following disclaimer in the documentation and/or other
 materials provided with the distribution.
 
-3. Neither the name of ZAMA nor the names of its contributors may be used to endorse
+3. Neither the name of Lux nor the names of its contributors may be used to endorse
 or promote products derived from this software without specific prior written permission.
 
 NO EXPRESS OR IMPLIED LICENSES TO ANY PARTY'S PATENT RIGHTS ARE GRANTED BY THIS LICENSE.
-THIS SOFTWARE IS PROVIDED BY THE ZAMA AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
+THIS SOFTWARE IS PROVIDED BY LUX AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
-ZAMA OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
+LUX OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
 OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
 ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

tests/fhevm-suite/e2e_old/.env.example

@@ -6,4 +6,4 @@ export PAYMENT_CONTRACT_ADDRESS=0xFb03BE574d14C256D56F09a198B586bdfc0A9de2
 export KMS_VERIFIER_CONTRACT_ADDRESS=0x9D6891A6240D6130c54ae243d8005063D05fE14b
 export GATEWAY_CONTRACT_ADDRESS=0x33347831500F1e73f0ccCBb95c9f86B94d7b1123
 
-export GATEWAY_URL="https://gateway-sepolia.kms-dev-v1.bc.zama.team/"
+export GATEWAY_URL="https://gateway-sepolia.kms-dev-v1.bc.lux.network/"