Hi all, I’m Hennadii, the solo developer behind titanhold.app, a small marketplace for AI-made work (images, video, bots, websites), based in Ukraine.
I’ve submitted a ZCG application for ZEC Order Pay: an MIT-licensed Python library and reference integration that lets web marketplaces accept shielded ZEC per order.
What it does
- A fresh shielded Unified Address and ZIP-321 payment URI/QR for every order
- Payment detection with a viewing key (UFVK) only, so no spending keys sit on the web server
- Order states (pending, paid, underpaid, expired, refunded), refunds to a buyer-provided shielded address, idempotent webhooks
- Batched creator payouts prepared as unsigned transactions (PCZT) and signed offline
- A live reference checkout on titanhold.app
Why it’s not another processor: it is aimed at Python/FastAPI/Django service marketplaces that don’t want to run BTCPay Server, and it can use CipherPay or zcash-walletd as a backend instead of duplicating them.
Ask: $36,000 over 4 milestones (M1 $6,000: public MIT repo, Rust UFVK scanner + Python alpha, and a testnet demo you can pay from Zashi/Ywallet; final milestone is a mainnet checkout on titanhold.app plus an external security review).
Honest status: titanhold.app is live, but no Zcash code exists yet. This is my first Zcash project, which is why M1 is small. TITANHOLD LLC (Wyoming) is in formation, with papers expected Oct 13-14.
- Application: Grant Application - ZEC Order Pay: shielded ZEC checkout, refunds and creator payouts for service marketplaces · Issue #489 · ZcashCommunityGrants/zcashcommunitygrants · GitHub
- Full proposal (PDF): https://titanhold.app/docs/zcash_proposal.pdf
I’d really welcome feedback, especially from the BTCPay plugin and CipherPay maintainers on how to avoid overlap. I’ll post monthly updates in this thread.
Thanks!
Hennadii