Primus

• Name: Primus
• URL: https://primuslabs.xyz/
• Category: zkTLS middleware / web-data attestation network / privacy-preserving offchain-data verification / identity-and-proof middleware
• Summary: Primus is proof middleware, not an identity hub. The real product is templated zkTLS attestations plus the attestor network, SDK defaults, and TEE-shaped operating stack around them. Useful rail, still not a category anchor.
• What it does:
  • Exposes zkTLS and encrypted-computation tooling for bringing offchain Web2 data into blockchain and AI workflows without revealing raw data
  • Offers two main zkTLS modes, MPC and Proxy, behind a unified developer-facing API surface
  • Uses developer templates and SDKs so applications can request attestations against predefined offchain data sources and proof rules
  • Supports both user-generated proof flows via browser extension and backend-generated proof flows where services act with user credentials
  • Frames identity verification, age-gating, nationality checks, address eligibility, and reusable KYC / proof-of-humanity-style attestations as initial application scenarios
  • Operates an attestor-node network with chain-specific task contracts and TEE-based deployment guidance, showing how proof generation is tied to real infrastructure operators
• Key claims:
  • The reusable thing is not zkTLS in the abstract. It is the templated attestation stack around it: templates, SDKs, attestors, and verifier defaults.
  • MPC mode versus Proxy mode is the real tradeoff surface. The docs make the security-versus-performance split clearer than the generic privacy marketing does.
  • The identity angle is narrower than the branding suggests. Primus is mainly a way to prove eligibility facts from web accounts and KYC-style data, not a full identity system.
  • The attestor docs matter because they expose the live choke points: Phala TEE deployment, supported chain contracts, and a team-run whitelist for node admission.
  • Keep the note because it shows a familiar crypto pattern in plain form: private proofs on paper, operator gating in practice.

Internal linkages

• Keep this on the strongest upward proof-stack reads: tlsnotary, reclaim-protocol, and vlayer.

Control surface

• The leverage sits in template authorship, attestor admission, TEE deployment, SDK defaults, and which proof modes apps normalize.

• Treat Primus as proof-orchestration middleware, not as an identity center.

• Whitepaper: No standalone Primus protocol whitepaper surfaced in this pass. The docs point instead to the team’s technical zkTLS foundation paper, Lightweight Authentication of Web Data via Garble-Then-Prove (IACR ePrint 2023/964), plus the QuickSilver paper as core technical references. See ../whitepapers/primus-primary-sources-2026-05-10.md.

• Sources:

  • https://primuslabs.xyz/
  • https://docs.primuslabs.xyz/
  • https://docs.primuslabs.xyz/primus-network/tech-intro/
  • https://docs.primuslabs.xyz/primus-network/attestor-node-guides/
  • https://docs.primuslabs.xyz/implementation-scenarios/verify-digital-identity/
  • https://github.com/primus-labs/zkTLS-tutorial
  • https://eprint.iacr.org/2023/964
  • https://eprint.iacr.org/2021/076

• Last reviewed: 2026-06-15 UTC