It’s been a few days since launching Gleyo during the ZecHub Hackathon, and I wanted to share a quick update on how things have been going.
Since launching on July 14, Gleyo has reached 33 weekly active users. It’s been exciting to watch people go through the full experience, from signing up and completing quests to chatting, earning shielded ZEC rewards, and withdrawing their rewards.
One thing that surprised me the most was the feedback around the UI/UX. Many testers mentioned that signing up and navigating the platform felt simple and intuitive, which was something I spent a lot of time trying to get right. I also refined the community payment flow to work seamlessly across both desktop and mobile devices, giving community owners a consistent experience regardless of how they choose to manage their communities.
Instead of focusing only on onboarding more users, I decided to slow down and iterate on the feedback I received, improving the parts of Gleyo that wouldn’t scale in the long run.
One major limitation is now solved
Originally, withdrawals were processed one user at a time across the entire platform.
That worked during development, but it obviously wouldn’t work once multiple communities started using Gleyo simultaneously.
I’ve now redesigned the withdrawal system into a queued architecture, allowing multiple withdrawal requests to be processed safely without overwhelming or crashing Nozy Wallet.
It’s one of those backend improvements that most users will never notice, but it’s essential if Gleyo is going to support many communities at once.
A feature inspired by community feedback
One piece of feedback from @squirrel really stood out.
He suggested allowing communities to fund campaigns using assets they already hold instead of requiring everything to start with ZEC.
I thought that made a lot of sense.
Since then, I’ve implemented multi-token deposits, allowing communities to fund campaigns with supported stablecoins like USDT and USDC, while Gleyo automatically settles rewards into shielded ZEC behind the scenes.
The goal isn’t to replace ZEC, it’s to make adopting Zcash much easier.
Communities can continue using familiar assets while contributors experience private payments through Zcash without additional complexity.
Going forward, I’ll continue expanding support for more tokens and networks to make onboarding even smoother.
Why I’m building Gleyo
My goal with Gleyo has never been just to build another community platform.
I want to help Zcash communities, Web3 projects, and even traditional Web2 organizations grow stronger communities through better onboarding, engagement, and long-term retention.
At the same time, I want to make Zcash feel almost invisible to newcomers.
Instead of asking someone to first understand wallets, shielded transactions, and privacy technology, communities can simply reward participation.
People join a community.
They contribute.
They earn rewards.
They experience private digital money.
Over time, they naturally discover the benefits of Zcash through using it, not because they were forced to learn it on day one.
That’s the experience I’m building toward.
Thank you
A huge thank you to @dismad for encouraging me to share Gleyo publicly after the hackathon.
Without that encouragement, a lot of the feedback, bug reports, feature requests, and conversations that have helped shape Gleyo over the past few days probably wouldn’t have happened.
Building in public has already made the project significantly better, and I’m incredibly grateful to everyone who has taken the time to test it.
Repository
https://github.com/gilmorre/gleyo-Zechub-
Telegram Task Verification
Community Conversations
