ZCASHORCHARDZSANU7 / TESTNET SUPPLY: PUBLIC · BALANCES: PRE-MAINNET ▮
Request access →
anon.garden ⁄ zcash shielded assets

Private money,
public proof.

Issue, transfer, and burn shielded assets on Zcash. Confidential balances, supply anyone can audit. Three primitives, one ledger.

Supply1,000,000.00
Block2,941,778
Holders
Balances
Amounts
Request access → Read the docs
Fig · Shielded poolpublic lattice ⁄ private ▮
nodes 64balances redacted
01Public ⁄ Privatethe core property

Transparent chains leak everything. Private chains can't prove anything. Zcash Shielded Assets give you both — existence, issuer, and total supply public; balances and transfers shielded.

ASSET ⁄ aUSD — ACME USDOn Zcash
Public · auditableVISIBLE
ExistsYES · ISSUED
Issuer ik0x00b9…c2
Total supply1,000,000.00
FinalizedNO
Private · shieldedREDACTED
Holders
Balances
Amounts
Counterparties
supply provable to anyone — balances visible to no one
02Three primitivesone small api
POST /assets

Issue

Mint a custom shielded asset. Supply is public and auditable; finalization caps it for good.

on-chain: supply auditable
POST /transfers

Transfer

Move units between shielded addresses. Amount, asset, sender, receiver — all hidden.

on-chain: fully shielded
POST /burns

Burn

Destroy units, reduce public supply. The off-board signal a bridge or auditor keys on.

on-chain: public decrement
03Why build hereprivacy you can audit
01

Public supply, private balances

Prove exactly how much exists while every holder's balance stays shielded. Impossible on a transparent chain.

02

Selective disclosure

Viewing keys turn private into private with an audit hatch — disclose a scoped view to a bank or regulator on demand.

03

Proof-of-reserves, native

Public supply makes the on-chain half of reserves trustless and real-time — wrapped supply provably ≤ collateral.

04

Authority, separated

Issuance keys are distinct from spend keys. A compromised mint key can't move funds; FROST / HSM custody fits day one.

05

One circuit, any asset

Custom assets move with the same privacy as ZEC through one proving circuit — no per-asset cryptography to trust.

06

We wrap the protocol

No node to run, no halo2 to implement. A stable API over the audited Zcash stack that outlives the alpha churn.

04What we're buildingapps on our base layer

anon.garden isn't only the base layer — we build the apps on it. Each one is issue, transfer, and burn composed with product logic and custody, sequenced by what's realistic on today's tooling.

Private PayrollTreasury

Pay salaries in a stablecoin on a schedule, per-employee amounts hidden. Why ZSA: no public salary ledger.

Building now — first app
Proof-of-ReservesEnterprise

Publish that on-chain supply is fully backed by attested reserves. Why ZSA: public supply makes the on-chain half trustless.

Building now
Stablecoin PaymentsPay

Send a USD-denominated shielded asset with amounts hidden — the "private USDC". Why ZSA: confidential transfers, auditable supply.

Status Next
Atomic-Swap OTCDeFi

Large asset-for-asset swaps settling in one atomic tx. Why ZSA: the swap primitive works today; no leaked size or counterparties.

Status Next
Lock-and-Mint BridgeBridge

Lock on origin, mint a wrapped shielded asset, burn to redeem. Why ZSA: auditable wrapped supply against locked reserves.

Status Later
Loyalty & VouchersLoyalty

Issuer mints points, users hold privately, redemption burns. Why ZSA: private balances, provable float, lowest complexity.

Status Later
The base layer enables far more than we'll build first-party — full catalog →
05How it worksyou call the api

A thin, durable service over the Zcash reference stack. It encodes every consensus obligation so your product never has to. Only the middle tier is ours.

YOUR APP Payroll Stablecoin Bridge Launchpad REST · issue / transfer / burn anon.gardenbase layer Issue/Xfer/Burn Key manager Wallet / sync Registry supply indexer · proof-of-reserves viewing-key disclosure · ZEC fee sponsorship JSON-RPC ZCASH Zebra node · OrchardZSA librustzcash · orchard halo2 proving · v6 tx
How it works — three tiers. The Zcash node, builder, and proving system are consumed from the audited reference stack, pinned to exact commits.
06Status ⁄ Roadmaplive on testnet
Phase 1Building

Base layer

Issue / transfer / burn API, key management, wallet sync, supply indexer, asset registry.

Phase 2Next

First product

A narrow, high-value back-office product — private payroll — end-to-end with a design partner.

Phase 3Later

Bridge

Custodial lock-and-mint with FROST custody and continuous proof-of-reserves, behind audit.

Phase 4Later

Composition

Open the platform: launchpad and a private DEX / OTC layer on the matured base.

▲ What we won't pretend

The reference tooling is alpha, the consumer wallet layer is still hardening, and Zcash Shielded Assets are pre-mainnet — activation in NU7 is subject to an active coinholder vote. We build on testnet, keep the boundary portable, and treat mainnet as a milestone, not a dependency. Privacy here is a boundary, not a blanket: issuance, supply, and burns are public; balances and transfers are private.

Build private money on Zcash.

Request access to the base layer, or read the full architecture and application catalog. Invite-only while it hardens on testnet.

Read the docs
Local demo form — no request is sent from this static page.