Paraloom is a privacy-focused Layer 2 on Solana. The shielded pool shipping in v0.5.0 — SOL bridges in, transfers move privately inside the pool, withdrawals settle back to Solana, all anchored by Groth16 zkSNARKs over BLS12-381 — is the foundation for the broader vision the banner names: privacy-preserving distributed compute. Sensitive workloads (order flow, model inference, anything where the inputs are themselves the leak) need a place to run where neither the public ledger nor a private operator sees them. Paraloom verifies the work via a validator network that learns nothing about the data, and anchors state on Solana for auditability.
The project is pre-mainnet. v0.5.0-rc2 is cut and runs on Solana devnet; the mainnet program ID rotates as part of the v0.5.0 final cut. The remaining gate to that final cut is the multi-party trusted setup ceremony for the Groth16 proving keys; everything else (peer discovery, coordinator HA, MPC tooling, signed releases with SBOMs and Sigstore) shipped in this release cycle.
| Repository | Visibility | What it is |
|---|---|---|
paraloom-core |
public | The L2 node, the bridge to Solana, the on-chain Anchor program, the privacy primitives, and the consensus layer. |
paraloom-app, paraloom-wallet, paraloom-dashboard, paraloom-docs |
private | Frontend, wallet, operator dashboard, and end-user documentation. Will open as the mainnet path consolidates. |
If you want to read the substance of what's being built, paraloom-core is the one repo that matters today.
- Privacy primitives. Pedersen commitments, Poseidon hashing, sparse Merkle trees, and Groth16 proofs over BLS12-381. Note construction, nullifier derivation, and proof codecs are implemented from scratch and pinned by property-based tests covering value conservation, hiding/binding, and inclusion-proof round-trips.
- Solana bridge. A deposit listener and a withdrawal submitter that talk to a deployed Anchor program. Replay protection on withdrawals is two-layered: a per-nullifier PDA and a caller-committed expiration slot.
- Consensus. Withdrawal verification by a validator quorum (default 7-of-10) with a slashing pipeline that flags equivocation as
SlashingEvidence::Equivocationand persistent unavailability as a streak. Reputation-gated quorum so validators below threshold are silently excluded. The validator role is intentionally verify-only and runs on commodity hardware — laptops, home PCs, single-board computers — so participation isn't gated on owning a server. - MPC trusted-setup tooling. Contributor / verifier / finalize CLIs, transcript chain, BGM17 contribution. Built to the audit's specification for the ceremony run.
- Coordinator HA. Active/passive failover with a recovery-time objective scenario test under 30 seconds.
v0.5.0-rc2 is published with binaries for Linux amd64 and macOS arm64, a SHA256SUMS file, an SBOM, and Sigstore signatures. The container image is built and signed.
Test coverage is the active focus. Current state — an on-chain unit-test suite, L2 invariants under property-based and Byzantine/partition scenarios, and a libfuzzer-driven nightly job — covers every shipping handler, the slashing pipeline end to end, and the attacker-facing seams: the proof and Merkle deserialise paths plus the WASM output bound check.
- The multi-party trusted setup ceremony with 20–30 contributors.
- External security audit of the privacy circuits and the Solana program.
- Container image hardening and the deploy guide.
After v0.5.0 lands, the private components above (paraloom-app, paraloom-wallet, paraloom-dashboard) open and the testnet program ID rotates to mainnet.
Issues and security disclosures: paraloom-core/issues.
MIT-licensed. All commits, releases, and ceremony transcripts are reproducible from the source tree.