4 Commits
Author SHA1 Message Date
zeekay ac15d6a0bd docs(workshop): point at luxfhe/torus (backend org) instead of luxfi/torus
All FHE backend infrastructure (Torus compiler, ML SDK, TFHE runtime,
KMS, FHEVM) lives under the luxfhe org. luxfi/* repos are reserved for
the Lux-blockchain integrated surfaces (precompiles, coprocessor, core
FHE Go library).
2026-05-29 14:18:22 -07:00
zeekay c52442c860 docs(workshop): drop Zama-derived workshop tooling
Removes:
  docs/workshop/fhevmjs/      (Zama JS package name; reencrypt + ABI demo)
  docs/workshop/pyfhevm/      (Python wrapper around fhevm-tfhe-cli)

Both directories shelled out to upstream tooling that isn't part of
the Lux stack — fhevmjs (Zama's JS SDK) and fhevm-tfhe-cli (Zama's
CLI for TFHE-rs). The clients were also broken on a clean checkout
since neither tool ships with this repo.

Workshop Solidity examples are unchanged (erc20.sol +
eip712-reencrypt.sol — these are stable references). README is
replaced with a placeholder pointing at the Torus compiler /
Lux FHE Coprocessor as the canonical client path; we will re-add
the workshop client when Torus ships.

Naming map followed for replacement copy:
  Lux FHE          — umbrella product
  Lux FHEVM        — canonical EVM product
  Lux FHE Precompiles, Coprocessor, GPU
  Torus            — compiler / framework brand
2026-05-29 13:53:17 -07:00
zeekay 2e1023cfdc Complete Lux FHE rebrand 2026-01-25 13:58:30 -08:00
zeekay 35b111984d Clean up: Move Go FHE implementation to lux/fhe
- Remove old Go FHE code (now in lux/fhe)
- Remove old Zama compatibility layers
- Update CI for TypeScript/JS SDK only
- This repo is now purely the @luxfhe npm package ecosystem
2026-01-02 10:53:28 -08:00