Zstellar Main
Zstellar Main · 01

The challenge

Stellar is fully transparent by design. Every payment, amount, and account balance is public and permanently indexed. For real-world payments — payroll, donations, vendor settlements — that transparency is a liability, not a feature. The existing options fall short: None of them offer a compliance-friendly anonymity set, where deposits can be gated by an approval list without de-anonymizing honest users.

The approach

User flow — Connect → Shield → Receive / Pay privately → Withdraw to public Proof flow (browser) — Derive keys → Build circuit inputs → Prove (Groth16) → Prepare Soroban tx On-chain flow

What we did

  • //001Connect Freighter on Testnet and fund with the in-app faucet if needed
  • //002Shield a public asset into the pool (you sign; tokens are pulled in and a note commitment is created)
  • //003Withdraw any time to a public G... address; the relayer submits, so your address never appears
  • //004Track every action through the proof stepper and the View-transaction explorer link
  • //005Derive keys from a single Freighter signature (cached locally in OPFS)
  • //006Build inputs from your unspent notes, the target amount, and the recipient
Zstellar Main · 04

Next case study

TrackFlow — Enterprise Supply Chain & Logistics Manager

Node.js, GraphQL, PostgreSQL, Next.js

Read