Skip to content
ZLAB
Solana · mainnet-beta

Sign in with your wallet

ZLAB never asks for a seed phrase or private key. Signing in shares your public address with this page only. Solana balances and transfers are public — connecting here does not make your on-chain activity private.

No Solana wallet was detected in this browser. Install a Wallet Standard wallet — Phantom, Solflare and Backpack all qualify — then reopen this dialog.

ZLAB does not link to wallet downloads: verify the source yourself before installing anything that holds keys.

Privacy Launchpad

Markets without
surveillance

Launch publicly. Participate privately. Settle with Zcash.

A token's name and its published rules belong in the open. The size of your position, the balance behind it, and the rewards you receive do not. Entry arrives over Solana, value settles through the Zcash shielded pool, and holder rewards land as shielded ZEC — with the market rules provable the whole way through.

Launch TokenExplore
Recent launches

The Network

Every token here sits on a published bonding curve with a fixed fee split. The ZEC figure is the share of trade fees routed to holders — the number that is specific to this launchpad.

Open the launchpad
Tokens launched
3
Volume 24h
$216.4K
Holders
653
ZEC to holders
7.7
Newest firstprices updating
Explore launches
How it works

Five steps, honestly labelled

Follow a position from a Solana wallet to a shielded ZEC reward. Two of these steps run today. Two do not exist. One is a typed adapter waiting for a provider.

STEP 01Live

SOL entry

You connect a Wallet Standard wallet. ZLAB verifies the RPC really serves the cluster it claims by checking its genesis hash, reads your balances, and routes swaps through the Jupiter aggregator — signed by your wallet, submitted on-chain.

Visible to everyone

Your Solana address, its balance, and every transfer it makes. This is ordinary public chain data.

Not published

Nothing yet. This step is not private and is not meant to be.

Three commitments

What ZLAB is for

Three commitments, each one testable. Trading is live today; the shielded layer is being built in the open, component by component.

01

Private by design

Positions are nobody else’s business.

Privacy is a property of the settlement layer, not a toggle in a front end. ZLAB settles participation through the Zcash shielded pool, where amounts and counterparties are never published — and until every layer lands, this interface names exactly which of your actions are visible.

Beta

Commitment notes, nullifier set and encrypted order flow — all five components specified.

02

Provable market rules

Published curve, published fees, checkable maths.

A launch commits to its bonding curve, graduation threshold and fee split before the first trade, and those terms are immutable afterwards. Privacy must not become an excuse for unverifiable accounting: the goal is settlement proofs that anyone can check without seeing a single participant’s position.

Beta

Curve, threshold and fee split published and enforced. Settlement circuit in design.

03

Rewards in shielded ZEC

Getting paid should not publish your income.

A token can route a fixed share of its trade fees to holders, paid in ZEC on a published cadence and weighted by how long the balance was actually held. Receipts land in the shielded pool, so a reward stream does not become a public salary.

Beta

Deterministic accounting, live today. Shielded payout rail rolling out.

Protocol stack

Six layers, one contract each

Every dependency sits behind a typed interface with a declared status.

Explore the stack
  1. 01LiveSolana entry adaptersolana-entry
  2. 02BetaConversion and routing adapterconversion-routing
  3. 03BetaZcash shielded settlement adapterzcash-settlement
  4. 04BetaPrivate asset and market layerprivate-markets
  5. 05BetaRewards enginerewards-engine
  6. 06BetaIndexer and APIindexer
Developers

Typed boundaries, no surprises

Every data path in this application goes through a schema-validated API and an adapter with a declared status. Nothing reaches the UI without saying where it came from.

Developer docs
HTTP APIzod-validated · rate limited
  • GET/api/statusMachine-readable implementation status
  • GET/api/tokensListings with filters, sort and pagination
  • GET/api/tokens/{id}/candlesOHLCV by timeframe
  • POST/api/quoteSOL → ZEC quote with expiry
  • POST/api/shielded-addressBech32m validation, nothing stored
  • POST/api/launch/previewValidates terms. Creates nothing.
Adapter contractsSix TypeScript interfaces covering entry, routing, settlement, private markets, rewards and indexing. Implement one, register the factory, done.
Implementation statusA component-by-component table of what is live, what is in beta and what is still being built — with the env keys that change each answer.
Threat modelWallet compromise, bridge custody, relayers, MEV, metadata leakage, timing correlation, reward claims and front-end compromise.

The objective

Public rules. Private positions.

Browse the network, track curve progress and watch rewards accrue. Trading is live; minting and shielded payouts open with mainnet. Every component states where it actually stands.

Explore LaunchesSee what is live