mirror of
https://github.com/luxfi/fhe.git
synced 2026-09-24 00:27:17 +00:00
zeekayandHanzo Dev
2069385603
Two thousand and twenty-one packages carried more than one spec across this estate — eslint alone in a hundred and four forms — and a package resolved twice is two copies at run time, which is how react-hook-form came to report "two different types with this name" from files nobody had edited. None do now. The number lives in the catalog: a manifest names the package, the workspace names the version. Where a manifest cannot reach a catalog it still carries the one version, because the table is the source either way. Co-authored-by: Hanzo Dev <[email protected]>
Data Seal - Verifiable Data Integrity
FHE-encrypted tamper-proof document sealing with three seal modes.
Implements: PIP-0010 / LP-0535
Seal Modes
| Mode | Description | Use Case |
|---|---|---|
| Public | Transparent, anyone verifies | Journalism, open records |
| ZK | Content hidden, properties provable | Trade secrets, proprietary models |
| Private | FHE-encrypted, selective disclosure | Whistleblower evidence, medical records |
How It Works
- Seal: Hash your document, encrypt an integrity tag with FHE, store on-chain
- Verify: Submit an encrypted challenge tag — homomorphic comparison reveals match/mismatch without exposing the original tag
- Batch: Seal thousands of documents in one transaction
Quick Start
npm install
npx hardhat compile
npx hardhat test
# Deploy
npx hardhat task:deploy-seal
# Create a seal
npx hardhat task:seal --contract <address> --hash 0xabc...
# Verify a seal
npx hardhat task:verify-seal --contract <address> --id 0 --tag 42
# Batch seal
npx hardhat task:batch-seal --contract <address> --count 10
Related
- Go implementation: github.com/luxfi/fhe/cmd/seal — Boolean-circuit FHE seal using XNOR+AND chain
- LP-0530: Z-Chain Receipt Registry (Poseidon2 Merkle accumulator)
- LP-3658: Poseidon2 Precompile (ZK-friendly hashing)