@paraloomlabs
Paraloom is a privacy-focused Layer 2 solution for Solana using zkSNARK (Groth16) shielded transactions and distributed compute. The project launched in March 2025 (<4 months old) with a working devnet, permissionless validator registration (21 validators already running on commodity hardware), and a live app for private swaps. Recent updates show rapid technical progress: on-chain proof verification, NAT traversal for home validators, trusted setup ceremony planned, and integration with Jupiter for shielded DEX swaps. The team operates with no VC backing and full transparency (open GitHub, public security reviews).
The early call
AI Analysispromising
Paraloom is a privacy-focused Layer 2 solution for Solana using zkSNARK (Groth16) shielded transactions and distributed compute.
The project launched in March 2025 (<4 months old) with a working devnet, permissionless validator registration (21 validators already running on commodity hardware), and a live app for private swaps.
Recent updates show rapid technical progress: on-chain proof verification, NAT traversal for home validators, trusted setup ceremony planned, and integration with Jupiter for shielded DEX swaps.
The team operates with no VC backing and full transparency (open GitHub, public security reviews).
Green flags: Working devnet with live app (app.paraloom.io) and 21 independent validators already operational · Technical substance: Groth16 zkSNARKs, BFT validator quorum, on-chain proof verification shipped, NAT traversal implemented · Genuinely early-stage: account <4 months old, 1.3k followers, pre-mainnet, bootstrapped with no VC backing · Open development: public GitHub (paraloom-labs/paraloom-core), transparent security reviews, documented progress updates · Low hardware barrier (runs on laptops/RPis) with permissionless validator registration already live
Red flags: No token yet despite active development (potential future monetization model unclear beyond validator fees) · Very small community (1.3k followers) creates limited network effects and scrutiny compared to established privacy projects · Pre-mainnet status means security assumptions not yet battle-tested in production environment
Recent tweetsSee all on 𝕏 →
Signal Timeline
Score breakdown0–100
Watching for additional signals.