We're Open Source: Four Repos, One Mission

Today marks a milestone for zNinja: we're fully open source.

We've just published four repositories under github.com/zNinjaPro that together form the complete stack for privacy-preserving transactions on Solana. This isn't a partial release or a "coming soon" promise—it's everything you need to understand, verify, and build on top of our shielded pool protocol.

Let's walk through what we shipped.

The Repositories

1. SDK

zNinjaPro/SDK — TypeScript

The SDK is the developer-facing interface to zNinja. It handles:

• Generating ZK proofs for deposits, withdrawals, and transfers
• Managing shielded notes and nullifiers
• Interacting with the on-chain program
• Merkle tree state synchronization

If you're building an application that integrates zNinja privacy, this is where you start.

2. Circuits

zNinjaPro/circuits — Circom

Zero-knowledge circuits are the cryptographic core of the protocol. Our circuits implement:

• Deposit proofs — prove you own a commitment without revealing the amount
• Withdrawal proofs — prove you can spend a note without revealing which one
• Transfer proofs — private-to-private value transfers inside the shielded pool

These are Groth16 circuits over the BN254 curve, designed for on-chain verification efficiency. The repo includes the Circom source, build scripts, and the proving/verification keys.

3. Program

zNinjaPro/program — Rust (Anchor)

The Solana smart contract that implements:

• A shielded token pool with Merkle tree commitment storage
• On-chain Groth16 proof verification
• Nullifier tracking to prevent double-spends
• Deposit and withdrawal instruction handlers

This is the trust anchor. Every privacy guarantee ultimately depends on this program behaving correctly—which is why we wanted it public and auditable.

4. Token Launch

zNinjaPro/token-launch — TypeScript

The deterministic SPL token launch tool we built for our own token. Features:

• Resumable deployment workflow (safe to retry)
• Arweave/Irys metadata uploads with hash verification
• Separate deploy and finalize phases
• Artifact-based state tracking

We wrote about this tool a few weeks ago. Now you can see exactly how it works.

Why Open Source?

Privacy tools demand transparency.

If you're trusting software to protect your financial privacy, you should be able to:

1. Read the code — no black boxes
2. Verify the cryptography — check the circuits yourself
3. Audit the on-chain logic — understand exactly what the program does
4. Build on top of it — extend, fork, integrate

We're not asking you to trust us. We're giving you the tools to verify.

What's Next

Open-sourcing the code is step one. Here's what follows:

• Documentation — comprehensive guides for developers integrating zNinja
• Security audits — third-party review of the circuits and program
• Community contributions — issues, PRs, and discussions are welcome
• Additional tooling — indexer, explorer integration, and more

The repositories are live now. Clone them, read them, run them.

If you find issues, open a ticket. If you have questions, reach out on X. If you want to build with us, the code is waiting.

---

Links:

• SDK
• Circuits
• Program
• Token Launch