KIOSK 22 | Looking for a few Zcash testers before our Colosseum submission

Zcash Apps
1

I’ve been building something on the Zcash side for the past few months, and I’m finally at the point where I’d rather let other people try to break the idea than keep staring at it myself.

It’s called KIOSK 22.

The basic problem we’re exploring is pretty simple. On public chains, a lot of launch protection depends on being able to watch wallets. Holder graphs, wallet history, fresh-wallet detection, bundle analysis and allocation tracing all rely on that visibility.

Once asset ownership becomes shielded, a lot of that visibility disappears.

So instead of relying on surveillance after the fact, K22 tries to move more of the protection into the launch mechanism itself.

We’ve been working on sealed participation, participant caps, reusable capacity, uniform clearing, duplicate participation rejection and deterministic success/failure handling.

We now have a judge-facing demo ready for the Colosseum Crypto World’s Fair. The part I care about most is that it doesn’t pretend everything already works on ZSA.

Every major part of the demo is clearly marked as PUBLIC TESTNET, LOCALLY PROVEN, SIMULATED or BLOCKED. Native settlement is still blocked on the current experimental stack, and the demo says so very clearly.

I’m looking for a few people from the Zcash community who haven’t been involved in the build to spend about three minutes with it without me explaining anything first.

Afterwards I’ll ask five simple questions:

  1. What problem do you think K22 is solving?
  2. Why does privacy change token launches?
  3. What part did you understand as simulated?
  4. What is currently blocked?
  5. Why is this different from simply putting a normal launchpad on Zcash?

If the answers are wrong, that’s useful too. It means the product isn’t explaining itself well enough yet.

If you’re technical and want to go deeper, even better. The demo produces a verifiable public transcript and the repo can independently reject tampering, so you don’t have to trust the frontend or take our word for it.

I’m specifically looking for honest criticism, not compliments.

If you want to test it, reply here or DM me and I’ll send the appropriate setup depending on whether you want the simple demo or the technical/reproducible version.