FHE16 as the engine layer
Explain the role of encrypted integer operations, bootstrapping, parameters, and benchmark profiles before exposing product APIs.
Developer documentation
This page is the public entry point for FHE16 technical documentation. The docs are split into paper reviews, product applications, and the FHE16 API so each area can grow independently.
The docs should read like technical product infrastructure, not a publication list. Each page ties research evidence to the methods, parameters, and trust boundaries a developer needs.
Explain the role of encrypted integer operations, bootstrapping, parameters, and benchmark profiles before exposing product APIs.
Keep method semantics stable across C, Web Browser/WASM, Rust, and Python. Language wrappers can be idiomatic without changing behavior.
Each paper gets a structured review: what the paper proves, what it means for the engine, what API behavior it supports, and what still needs implementation evidence.
Anchor paper for the low-latency FHE16 narrative and the benchmark claim that encrypted computation can be practical for product workloads.
Connects arithmetic circuits to API methods such as add, lt, max, and select.
Supports correctness, noise budget, and parameter documentation for reliable FHE16 execution profiles.
Frames SSFHE, threshold disclosure, and multi-party workflows beyond a single-party encrypted compute setup.
Product docs should show which encrypted operations are used, what data stays private, and where a user or verifier sees the result.
Compute or verify over encrypted state while allowing threshold or policy-based disclosure when a protocol requires a result.
Keep bids hidden while computing winner selection with encrypted comparison, max, and conditional selection methods.
Score sensitive insurance, identity, account, or transaction data without exposing raw records to the compute operator.
Aggregate or compare encrypted preference signals while limiting raw customer data movement across the product stack.
The API docs now start from FHE16Ver6's current C ABI. The API overview stays short, and each operation has its own page with caller, circuit, and ownership notes.
Core methods stay consistent across language bindings. Each method also needs a caller definition and a circuit path so product teams know who invokes it and what homomorphic structure runs.
FHE16_GenEvalruntime and key initFHE16_ENCIntinteger encryptionFHE16_DECIntinteger decryptionADD / SUB / SMULLarithmeticLT / LE / GT / GE / EQcomparisonMAX / MIN / SELECTcompose// Current C ABI direction.
int32_t* sk = FHE16_GenEval();
int32_t* a = FHE16_ENCInt(42, 8);
int32_t* b = FHE16_ENCInt(100, 8);
int32_t* less = FHE16_LT(a, b);
int64_t opened = FHE16_DECInt(less, sk);
FHE16_Free(less);The docs source separates binding pages so each SDK can grow with its own examples, ownership rules, and API notes.
Client-side demos and browser-native encrypted computation experiments using a WASM wrapper.
The lowest stable boundary for FFI, integration tests, and wrappers in other languages.
Typed resource management over the C ABI with explicit ownership and error handling.
Research notebooks, product prototypes, and benchmark orchestration against the same method semantics.