The current docs make clear that SP1 should be treated as a distinct runtime layer beneath the broader Succinct network/company entry. The important surfaces are not just a zkVM exists, but which proof forms it emits, how recursion is used, and which optimizations are exposed to developers.
The What is a zkVM? page gives the clearest concise architecture summary: RISC-V program execution, STARK-based proving over the Baby Bear field, recursive proof composition, and STARK-to-SNARK compression for onchain verification.
The proof-types docs expose a concrete verification-economics menu — default STARK, compressed, Groth16, and PLONK — which is useful for comparing SP1 against other proving stacks whose practical adoption depends on proof size, gas, and trusted-setup tradeoffs.
The precompiles docs reveal an important control surface that generic summaries usually miss: Succinct curates patched cryptography crates and precompile support, which affects which workloads become efficient in practice.
The public README reinforces that SP1 is production-facing and large-workload-oriented rather than a toy SDK, citing support for big Rust programs and listing multiple external audits.
No standalone SP1 whitepaper surfaced in this pass. The broader Succinct whitepaper is parent-stack context, but the docs and repo are the clearest current primary sources for SP1 specifically.