Segment 3
In this sub-session, the assistant conducted an exhaustive investigation to plan a pipelined SNARK proving daemon called cuzk. The work began by reading all seven prior optimization proposals and background documents to understand the full architecture, then systematically explored every layer of the existing system: the ffiselect child process model for GPU proving, SRS/parameter loading paths across all proof types (PoRep, SnapDeals, WindowPoSt, WinningPoSt), the supraseal C2 C++/CUDA API surface, the bellperson supraseal prover internals, and the circuit sizes and resource profiles for each proof type. The assistant also studied GPU inference engine architectures (vLLM, Triton, TensorRT-LLM) for patterns in model loading, memory management, and scheduling—drawing direct analogies between model weights and SRS parameters, inference requests and proof jobs, and KV cache and witness vectors. Finally, the assistant verified the golden test data in `/data/32gbench/` and explored `lotus-bench simple` commands for generating vanilla proofs for all proof types. The culmination of this research is the **`cuzk-project.md`** document written to the repo root, which lays out a complete architecture and phased implementation plan covering gRPC API, SRS memory manager, scheduler, GPU worker pipeline, testing utility, and an 18-week roadmap.
From Investigation to Architecture: Designing cuzk, a Pipelined SNARK Proving Daemon for Filecoin