What is happening
in Poulpy.

Most of the work since 0.8.3 went into the hardware abstraction layer: a smaller API surface, explicit contracts, derived defaults, and a single-backend path through the OEP. Sparse operands and the hot-path rework came out of the same pass, along with the CKKS canonical scale and Windows support.

Bring questions, or something you are building — the second half of the call is open.

Phantom is as old as Poulpy. It has been running on the library since an early build, and its virtual machine still depends on the HAL, core, scheme operations and CPU backends.

It now has a page here explaining what it actually does: how a Rust program becomes an encrypted RISC-V binary, and what stays hidden while it executes — the instructions, the constants and the machine state, not just the inputs.

The CPU backends are now multithreaded, and another optimization pass landed on top of it: CKKS bootstrapping runs in 2.3s on 16 threads and 5.5s on a single thread. Normalization was reworked, partial limbs are canonicalized in linear transforms, and functional bootstrapping now handles non-power-of-two inputs.

This release also ships the site you are reading, with the guides, the architecture walkthrough and a benchmark table you can filter by scheme, operation and backend.