[Grant Application] TIPZ: Shielded Pool Growth Through Creator Tipping
Summary: TIPZ is a live, non-custodial tipping platform where every tip arrives as shielded ZEC. Fully private ZEC-to-ZEC payments are integrated via Zodl, alongside cross-chain on-ramps from ETH, USDC, USDT, and SOL via NEAR Intents.
Grant type: Retroactive + Prospective
Amount requested: $50,000 USD (payable in ZEC)
Team: naly (@defi_naly), Founder, Strategy & Product | Franz, Lead Developer, Architecture & Security
The Problem
Every major tipping platform surveils creators by default.
Ko-fi, Buy Me a Coffee, and PayPal route every transaction through payment processors that log sender, receiver, amount, and timestamp. That data gets sold, subpoenaed, or leaked. Transparent crypto is worse: Bitcoin and Ethereum record every tip permanently on public block explorers, linkable to real identities through exchange KYC, ENS names, and on-chain analysis firms like Chainalysis.
For creators (journalists, activists, independent voices), this isn’t abstract. A political journalist’s supporter list becomes a target list. An artist’s income becomes public record. A whistleblower’s patron becomes identifiable. Financial surveillance chills the very expression these platforms claim to enable.
Zcash shielded addresses solve the privacy problem at the protocol level. But there’s a gap between “here’s a 78-character unified address” and “click this link to support my work.” That gap is where adoption dies, and it’s what TIPZ closes.
Why Now
You built the protocol. Now it needs a product layer.
Zcash developers have spent nearly a decade shipping the most advanced privacy technology in crypto: Sapling, Orchard with Halo 2, and now Tachyon, pushing toward oblivious synchronization and thousands of shielded transactions per second. The protocol is approaching maturity. The question has shifted from “can we build private money?” to “who will use it?”
Micropayments and privacy are crypto’s two clearest product-market fits. Micropayments remove friction from small-value transfers that traditional payment rails can’t handle economically. Privacy protects financial data that public blockchains expose by default. TIPZ sits at the intersection of both: private micropayments for creators, built on infrastructure that finally makes it possible.
The answer isn’t more cryptography. It’s a product layer. The protocol infrastructure is proven: Zodl handles shielded transactions, NEAR Intents routes cross-chain swaps, and the Zcash network provides the privacy guarantees. What’s missing is the consumer application that makes all of it accessible to people who aren’t cryptographers.
TIPZ is that layer. Not reinventing payment infrastructure, but building the user-facing social product that turns a decade of protocol work into something creators touch every day. Without it, the shielded pool stays small and transaction volume stays theoretical.
What TIPZ Is
Creators get a tip page where every payment arrives as shielded ZEC. 0% platform fees. No middleman cut. The creator receives everything.
TIPZ doesn’t build payment infrastructure. It builds vertically on proven infrastructure: Zodl for shielded payments, and NEAR Intents for cross-chain routing. The value TIPZ adds is the consumer experience layer (registration, tip pages, dashboards, notifications, promotion tools) that turns existing infra into a product people actually use.
Here’s how it works:
-
Creators register by signing in with X (Twitter OAuth) and entering a Zcash unified address. Two steps. They now have a live tip page at
tipz.cash/[handle]. -
Supporters tip through two payment paths:
-
ZEC Direct Send (live): Fully private. TIPZ generates a ZIP-321 compliant
zcash:URI and QR code. The tipper completes the payment in their Zcash wallet of choice (Zodl, Zecwallet, or any shielded-capable wallet). The result is a standard shielded-to-shielded transaction on the Zcash network: no intermediary, no public record linking sender to receiver. The privacy guarantee comes from the Zcash protocol itself; TIPZ just makes it accessible through UX. This is the privacy path, and it’s live today. -
Cross-chain via NEAR Intents (live): The convenience path. The supporter connects a wallet (MetaMask, Rabby, or Phantom), picks an amount, and pays with crypto they already hold: ETH, USDC, USDT, or SOL across Ethereum, Polygon, Arbitrum, Optimism, and Solana. NEAR’s cross-chain intent protocol routes the payment and delivers ZEC to the creator’s shielded address. (See Privacy Model below for what is and isn’t private in this path.)
-
-
Creators get notified in real time for cross-chain tips, which are trackable on public networks. The authenticated dashboard at
tipz.cash/myshows total cross-chain earnings, tip history with decrypted messages, ZEC/USD conversion at live price, and promotion tools (share links, pre-filled tweets, image stamp generator). ZEC Direct tips bypass the platform entirely.
Cross-chain for seamless ZEC onboarding. ZEC Direct for full protocol privacy. 0% fees on both.
Growth Strategy
- Phase 1 (now): Privacy-native creators. The Zcash community, crypto-privacy advocates, and creators who already value sovereignty. They get the value immediately.
- Phase 2: Broader creator market. Any X creator tired of platform fees and financial surveillance. The 0% fee is the wedge: a concrete, dollar-denominated reason to switch. Cross-chain tipping via NEAR Intents means their audience tips from whatever chain they’re already on, and the ZEC onboarding happens invisibly.
- Phase 3: Fiat-to-shielded via Mesh. Tippers connect exchange accounts (Coinbase, Kraken, Gemini) and tip directly from fiat or exchange balances. No self-custody wallet needed. A non-crypto-native supporter clicks a link, connects their exchange, and ZEC arrives shielded. TIPZ becomes a fiat-to-shielded-ZEC funnel.
Each phase pulls more value into the shielded pool from further outside the Zcash ecosystem.
Long term, the model extends beyond X. Substack is a clear next target: rather than locking readers behind subscription paywalls, creators can earn tips on individual pieces of content. Same privacy, same zero fees, applied to long-form writing. The model works anywhere creators publish; X is just the first surface.
What’s Been Built
TIPZ is live. Cross-chain payments are operational in production via NEAR Intents. ZEC-to-ZEC payments are integrated via ZIP-321 and any Zcash shielded wallet.
A two-person team shipped a production-ready platform in months using AI-augmented development: modern AI tools for rapid prototyping on proven infrastructure (Next.js, Supabase, NEAR Intents), followed by Franz auditing and re-architecting the entire codebase for privacy and security. The result is a production platform with two payment paths, five chains, encrypted messaging, and 142 tests, shipped at a fraction of typical cost.
What’s Live
| Feature | Status | Why It Matters |
|---|---|---|
| Creator registration (X OAuth + unified address) | Live | Each registration = 1 new Zcash wallet user |
Tip pages (tipz.cash/[handle]) |
Live | Shareable links that funnel directly to shielded transactions |
| ZEC Direct Send (QR code + ZIP-321 URI) | Live | Fully private shielded-to-shielded tipping, zero intermediaries |
| Cross-chain payments (NEAR Intents, 5 chains, 4 tokens) | Live | On-ramps ETH/USDC/USDT/SOL holders into ZEC |
| Creator dashboard (real-time notifications, earnings, tools) | Live | Keeps creators engaged and promoting their tip links |
| Creator directory (search, leaderboard, activity ticker) | Live | Public proof of ecosystem growth |
| Encrypted tipper-to-creator messaging (RSA, IndexedDB) | Live | Private communication between supporter and creator |
| Dynamic OG images for creator profiles | Live | Social sharing drives organic discovery |
| ZEC price ticker (CoinGecko, with fallback) | Live | Real-time USD conversion in dashboard and tip flow |
Technical Architecture
Payment Flows
ZEC Direct Send (leverages existing Zcash wallet infrastructure):
Tipper opens creator's tip page
→ Selects "ZEC Direct" and amount
→ TIPZ generates ZIP-321 zcash: URI with amount + memo
→ QR code displayed (scannable by Zodl, Zecwallet, or any shielded-capable wallet)
→ Tipper completes payment in their wallet of choice
→ Standard shielded-to-shielded Zcash transaction (protocol-level privacy)
→ Creator receives ZEC. TIPZ has no visibility into the transaction
Note: TIPZ generates the payment request. The privacy guarantee comes from the Zcash protocol, not from TIPZ. The tipper’s wallet handles the actual transaction.
Cross-Chain via NEAR Intents:
Supporter connects wallet (MetaMask / Rabby / Phantom)
→ Selects amount + token (ETH, USDC, USDT, SOL)
→ TIPZ requests quote from NEAR Intents API
→ Supporter signs transaction to NEAR deposit address
→ NEAR Intents executes cross-chain swap
→ ZEC arrives at creator's shielded address
→ Creator receives real-time notification
Tech Stack
- Frontend: Next.js 16, React 19, TypeScript, Tailwind CSS
- Backend: Supabase (PostgreSQL + Realtime WebSocket)
- Web3: ethers.js (EVM), @solana/web3.js (Solana), NEAR Intents (cross-chain routing)
- Auth: Twitter OAuth 2.0 PKCE
- Encryption: RSA key pair per creator (private key in IndexedDB, never leaves device)
Core Libraries
| File | Lines | Responsibility |
|---|---|---|
lib/wallet.ts |
1,323 | Wallet connection, EIP-6963 multi-wallet detection, chain switching, transaction execution |
hooks/useTipping.ts |
921 | Tipping state machine (12 states), localStorage persistence, exponential retry |
lib/near-intents.ts |
464 | NEAR Intents 1Click API: quoting, execution, status polling |
Supported Chains & Wallets
| Token | Chains | Wallets |
|---|---|---|
| ETH | Ethereum, Arbitrum, Optimism | MetaMask, Rabby |
| USDC | Ethereum, Polygon, Arbitrum, Optimism | MetaMask, Rabby |
| USDT | Ethereum, Polygon, Arbitrum, Optimism | MetaMask, Rabby |
| SOL | Solana | Phantom |
| ZEC | Zcash (direct) | Zodl, Zecwallet |
Privacy Model
Creators choose to be visible. Their earnings and supporters shouldn’t be. That’s the privacy model TIPZ is built around, and we’re transparent about where it delivers today, where it falls short, and what we’re doing about each gap.
Who Privacy Protects, and Who It Doesn’t
The goal is full privacy for both sides. For ZEC Direct tips, that’s already real: shielded-to-shielded, no public record, no link between tipper and creator. For cross-chain tips, it’s not there yet. A tipper paying from MetaMask or Phantom is transacting on a public chain; their wallet address, balance, and full transaction history are visible to anyone. NEAR’s Confidential Intents will hide the routing step that currently exposes cross-chain tippers. Until then, the privacy promise is fully delivered only on the ZEC Direct path.
Creators choose to be discoverable, not exposed. A creator registers with their X handle and shares their tip page at tipz.cash/[handle]. That much is public, they’re saying “I accept tips here.” But their wallet balance, transaction history, and what they do with received ZEC remain shielded. No one can see how much a creator has earned, how many tips they’ve received, or where funds go after arrival. The creator’s identity as a recipient is public. Their finances are not.
Payment Path Privacy
ZEC Direct Send (live), full protocol privacy. The tipper sends ZEC directly to the creator’s shielded address using their Zcash wallet of choice (Zodl, Zecwallet, etc.). TIPZ generates the ZIP-321 payment request; the wallet and the Zcash protocol do the rest. The entire transaction stays inside the shielded pool. We have zero visibility: who tipped, how much, when.
Cross-chain via NEAR Intents (live), convenience path, partial privacy. Most potential supporters don’t hold ZEC. They hold ETH, USDC, USDT, or SOL. NEAR Intents routes any supported token into the creator’s shielded address, converting non-private assets into private ones in a single step. Every cross-chain tip means another deposit of ZEC into shielded addresses, from people who may never have used Zcash before.
What’s visible today: The source transaction on the origin chain (e.g., Ethereum), the NEAR routing step, and the destination shielded address are all observable on their respective explorers. A motivated observer can trace: tipper wallet → NEAR deposit address → creator’s shielded address.
What this means: Cross-chain tips are meaningfully more private than PayPal, Ko-fi, or on-chain Bitcoin/ETH (which expose amounts, identities, and full transaction graphs permanently), but the routing is observable. Supporters who already hold ZEC should use ZEC Direct for full privacy. Cross-chain is the on-ramp for everyone else.
Platform-Level Data: What TIPZ Stores and Why
We want to be direct about this because it’s the question we’d ask if we were reviewing this grant.
TIPZ stores a mapping of X handles to Zcash unified addresses in Supabase (PostgreSQL). This is the creator directory, and it’s what makes tipz.cash/[handle] work. Every registered creator has their X identity linked to their receiving address in our database.
What this means: If Supabase were breached or subpoenaed, an attacker would obtain the set of X handles and their associated Zcash addresses. For creators, this is the same information they already publish voluntarily on their tip pages. For supporters using ZEC Direct Send, no tipper data exists in our system at all; those transactions are entirely on-chain and shielded. For cross-chain tippers, TIPZ stores tip records with financial data (amounts, memos) RSA-encrypted. Only the creator can decrypt using their private key stored in IndexedDB. Row metadata (creator ID, status, timestamp) is retained unencrypted for dashboard functionality.
Why it’s built this way today: TIPZ is a v1 product built by two people. We chose Supabase for development speed, real-time WebSocket support, and authentication infrastructure. Building a decentralized identity layer before shipping a working product would have been premature optimization: a more private architecture with zero users. The pragmatic path was to ship the product, prove demand, then progressively decentralize.
What we’re not storing: We don’t store wallet addresses of tippers, browsing history, or browser fingerprints. Server-side, console.log is stripped in production builds (Next.js removeConsole). Only errors and warnings reach Vercel logs, with sensitive data redacted. Encrypted messages use RSA keys generated client-side with private keys stored in IndexedDB; they never touch our server. We hold no funds at any point.
Static Address Reuse: A Known Limitation
Each creator currently registers a single Zcash unified address. All tips, both ZEC Direct and cross-chain, arrive at this same address. This means:
- Cross-chain tips to the same creator are linkable at the destination. An observer who identifies one tip to a creator’s address can associate all future inflows to that address.
- For ZEC Direct, the Zcash shielded pool still protects sender privacy (the tipper is hidden), but the creator’s receiving address is a single static target rather than a fresh address per payment.
This is a well-understood privacy anti-pattern, and we’re addressing it as a priority.
Privacy Roadmap: Concrete Next Steps
These aren’t aspirational. They’re scoped work items, and prospective grant funding is partly allocated to them.
1. Unique address per payment (active priority). We aim to integrate diversified address generation (a fresh receiving address for each tip) through collaboration with Zodl and other Zcash wallet developers. This breaks the linkability of cross-chain tips at the destination and strengthens ZEC Direct privacy further. It requires wallet-side support for address derivation from a single unified address. Initiating this collaboration is a near-term priority and a core use of prospective funding.
2. NEAR Confidential Intents integration (awaiting API). NEAR announced Confidential Intents at NEARCON (February 25, 2026), a privacy layer that runs cross-chain swaps on a dedicated private shard, hiding swap details (source token, destination address, amount) from public observers during routing. This directly addresses the cross-chain routing visibility problem. We’re monitoring the rollout and will integrate as soon as a public API endpoint is available.
3. Data minimization and platform hardening. Reduce what TIPZ stores to the absolute minimum required for the product to function. Cross-chain tip records already persist with financial data (amounts, memos) RSA-encrypted at rest. Only the creator can decrypt. Row metadata (creator ID, status, timestamp) remains readable for dashboard queries. Ongoing work: audit all stored fields, eliminate anything not strictly required, and harden access controls. The goal is a model where TIPZ facilitates the connection but retains the minimum state necessary.
4. Long-term: decentralized identity layer. The end state is a system where the X handle → Zcash address mapping doesn’t depend on a centralized database at all. Potential paths include on-chain registries, Nostr-based identity, or integration with emerging Zcash identity standards. Longer-horizon effort. We’re naming it here for transparency, not claiming it’s imminent.
The Honest Summary
| Layer | Privacy Today | Target State |
|---|---|---|
| ZEC Direct Send (tipper → creator) | Full protocol privacy. Shielded-to-shielded, TIPZ has zero visibility. | Same. Already at the gold standard. |
| Cross-chain routing (tipper → NEAR → creator) | Partial. Source tx and routing are observable on public chains. | Confidential Intents hides routing details on NEAR’s private shard. |
| Destination address linkability | Weak. Single static address per creator; all tips are linkable at destination. | Unique address per payment breaks linkability. |
| Platform data (Supabase) | Centralized. X handle → Zcash address mapping in managed PostgreSQL. Tip financial data RSA-encrypted at rest. | Continued data minimization + decentralized identity long-term. |
| Tipper identity (ZEC Direct) | None stored. TIPZ has no knowledge of who tipped. | Same. |
| Tipper identity (cross-chain) | Tx records stored (financial data RSA-encrypted, only creator can decrypt). Tipper wallet address visible on source chain. | Encrypted at rest + Confidential Intents to reduce on-chain exposure. |
We shipped a working product with honest tradeoffs rather than sitting on a perfect privacy architecture with no users. Every item on this roadmap moves TIPZ closer to the standard the Zcash protocol makes possible. We’d rather build in the open and improve iteratively than overpromise.
Grant Request
Total: $50,000 USD (payable in ZEC)
Split as $30,000 retroactive (work already completed and shipping) + $20,000 prospective (growth and operations).
Retroactive: Development ($30,000)
This covers the live product: a working tipping platform with two payment paths (ZEC Direct + cross-chain), encrypted messaging, real-time notifications, creator dashboard, and production payments. Built for privacy, audited for security, deployed at zero platform fees.
| Line Item | Amount | Details |
|---|---|---|
| Product development | $20,000 | Design, engineering, two payment paths, cross-chain integration (5 chains, 4 tokens, 3 wallets), encrypted messaging, real-time dashboard, 142 tests, production deployment |
| Security audit & privacy architecture | $7,000 | Full codebase audit by Franz, non-custodial payment hardening, shielded-first architecture, RSA encrypted messaging |
| Infrastructure & operations | $3,000 | Supabase, CI/CD, hosting, NEAR Intents API integration |
Prospective: Growth & Operations ($20,000)
The product is built. This funds the transition from working product to growing ecosystem tool.
| Line Item | Amount | Details |
|---|---|---|
| Engineering | $8,000 | Continued development: Confidential Intents integration, Mesh connectivity, subscriptions, request payment links, privacy improvements |
| Marketing & community growth | $9,000 | Creative campaigns to build a closely aligned Zcash creator community, demo content, ecosystem engagement, creator outreach and onboarding incentives |
| Infrastructure | $3,000 | Supabase Pro, hosting, X API access, monitoring (6 months) |
Why This Amount
-
Retroactive ($30k): We’re not billing for lines of code. We’re asking for recognition of a live, shipping product built to drive shielded pool growth, cross-chain ZEC acquisition, and new wallet users. A two-person team shipped a production-ready platform (two payment paths, five chains, four wallets, encrypted messaging, real-time dashboard) at a fraction of typical development cost. AI-augmented development made the velocity possible, but product design, security architecture, and privacy engineering required real human expertise.
-
0% platform fee means we forgo revenue by design. Every dollar of every tip goes to the creator. The architecture supports a fee switch. We deliberately choose not to flip it because growing the shielded pool matters more than revenue right now. Grant funding is our only funding model: no VC, no token, no platform fees.
-
Prospective ($20k): Creator acquisition is the core deliverable. 250 new wallet users at ~$80/user is cheaper than any app install campaign, and each creator generates recurring shielded transactions from their audience.
Milestones
Milestone 1 (Retroactive, upon approval): $30,000
Deliverable: The live TIPZ platform as described above.
Evidence:
- Live deployment at tipz.cash
- ZEC Direct Send fully operational (QR code, ZIP-321 URI, wallet-agnostic)
- Cross-chain payments verified (ETH, USDC, USDT, SOL → shielded ZEC)
- Creator registration, dashboard, directory, encrypted messaging all functional
Acceptance criteria: ZCG committee can verify the live product, review the codebase, and confirm feature completeness.
Milestone 2 (Month 1-2): $10,000
Deliverable: 100 registered creators + request payment links.
Key results:
- Demo video published
- 100 creators registered with verified X handles and Zcash unified addresses
- 100 new Zcash wallet users (each creator = 1 wallet install)
- Request payment links: creators generate shareable links (
tipz.cash/[handle]?amount=5) with pre-filled tip amounts for invoicing, merch sales, and pay-what-you-want content. Each link funnels directly to a shielded transaction. - NEAR Intents Confidential Intents integration (contingent on API endpoint availability): encrypt cross-chain swap payloads so that tip routing details are hidden from public observers, significantly improving privacy for non-ZEC tippers.
- Zodl wallet recommendations integrated in registration and tipping flows
- Explore wallet integrations for unique-address-per-payment to improve cross-chain privacy
- Community engagement: Zcash Discord presence, forum updates
Acceptance criteria: 100+ shielded addresses receiving tips, verifiable through the public creator directory. Request payment links functional. Confidential Intents integrated if API available.
Milestone 3 (Month 3-4): $10,000
Deliverable: 250 registered creators + Mesh integration + subscriptions.
Key results:
- 250 total registered creators (250 Zcash wallet users)
- Organic sign-ups exceeding outreach-driven registrations
- Mesh integration: tippers connect exchange accounts (Coinbase, Kraken, Gemini) to tip directly from fiat or exchange balances without needing a self-custody wallet. This removes the biggest friction point for non-crypto-native supporters and opens a direct fiat-to-shielded-ZEC on-ramp, turning TIPZ into a ZEC acquisition funnel for audiences who have never touched Zcash.
- Subscriptions: recurring scheduled tips (weekly/monthly). Each subscription generates recurring shielded transactions automatically, turning one-time supporters into a sustained source of shielded pool activity.
- Monthly ecosystem update posted to Zcash forum
Acceptance criteria: 250+ creators in directory, Mesh payments operational, subscriptions generating recurring shielded transactions, referral tracking live, public progress report.
Team
naly
Role: Founder, Strategy, Product & Growth
Five years building user-facing products in DeFi. At Beets: helped grow the protocol to become the largest DEX and LST on the network, the only protocol to achieve both. Worked on strategy, BD, marketing, and partnerships. At Balancer: led marketing strategy for the Balancer v3 launch and forged key partnerships, including Aave’s Boosted Pools integration. Broad experience across the full stack of decentralized financial primitives (DEXs, lending markets, validators, liquid staking tokens), focused on the strategy and growth side. Now returning to cypherpunk values to contribute to what matters most in the age of AI: private payments. Creator in his own right. X articles, threads, and a Substack newsletter with 1,000+ subscribers. Understands the creator economy from the inside: the friction, the surveillance, the platform capture. Conceived TIPZ, designed the product and UX, used AI-augmented development to rapidly prototype a working application on proven infrastructure, then brought in Franz to harden it.
Franz
Role: Lead Developer, Architecture & Security
Development background at Beets and Balancer with deep experience in DeFi protocol engineering: AMM innovation, lending market integrations, and liquid staking tokens. Actively runs and maintains key DeFi applications, giving him hands-on experience across the full stack of decentralized financial primitives (DEXs, lending markets, validators, LSTs). Prior career in traditional financial rails before moving into the decentralized ecosystem. Audited the entire TIPZ codebase and re-architected the system with privacy and security as the primary design constraint: encrypted messaging (RSA with IndexedDB key storage), non-custodial payment flow, shielded-first architecture.
Risks and Mitigations
| Risk | Impact | Mitigation |
|---|---|---|
| NEAR Intents reliability or downtime | High | ZEC Direct Send is live as an independent payment path with no dependency on NEAR. Circuit breaker implemented. |
| Low creator adoption | High | Start with Zcash community (natural fit), then expand. Onboarding incentives de-risk early adoption. Retroactive portion is not dependent on adoption metrics. |
| Regulatory concerns | Medium | Non-custodial design. TIPZ never holds or transmits funds. We operate as a directory and notification service. No money transmission. |
| “Why fund a 2-person team?” | Medium | The live product is the answer. 142 tests, 19 API routes, two payment paths, encrypted messaging, all shipping. AI-augmented development is a force multiplier, not a quality compromise. Franz’s security audit ensures production-grade code. |
| Cross-chain routing visibility | Medium | Transparently disclosed in Privacy Model. ZEC Direct Send is fully private today. NEAR’s Confidential Intents (announced Feb 2026) will encrypt swap payloads, and we’re awaiting the API endpoint. Unique-address-per-payment is an active parallel priority. |
| X/Twitter API changes | Low | Core product functions without X API. OAuth is the only dependency, and a manual verification fallback exists. |
Why This Benefits Zcash
-
Shielded pool growth. Every tip arrives at a shielded address. 250 creators receiving tips means recurring shielded volume; subscriptions compound it automatically.
-
New wallet users. Every creator registration = 1 new Zcash wallet install. 250 new wallet users in 4 months, directly measurable.
-
ZEC onboarding engine. ETH, USDC, USDT, SOL holders are funneled into shielded ZEC through real utility, not speculation. Mesh adds fiat next.
-
Creator advocacy. A creator earning ZEC tips becomes an organic Zcash advocate to their entire audience. Every “tip me privately” tweet is free ecosystem awareness.
-
“Get paid privately for your work” is more compelling than “store value privately.” TIPZ gives Zcash a use case that resonates with exactly the people (journalists, artists, independent voices) who make privacy tangible.
-
The product layer the protocol needs. A decade of cryptographic breakthroughs needs consumer applications to reach real users. TIPZ adds the social layer that turns protocol capabilities into something creators touch every day.
Links
- Live product: tipz.cash
- Creator directory: tipz.cash/creators
- Repository: github.com/tipz-cash/tipz.cash (MIT license, public)
- X Account: tipz_cash
Closing
The Zcash community has spent a decade building the strongest privacy technology in crypto.
What comes next are products that put that technology in the hands of people who need it. Creators who deserve to earn without surveillance. Supporters who deserve to give without a record.
TIPZ makes that real. It’s live today. Two payment paths, one fully private, one convenient. Zero platform fees. Non-custodial. Every tip grows the shielded pool. Every creator registration adds a wallet user to the ecosystem.
We built it lean, we built it honest, and we shipped it. What we’re asking for is straightforward: recognize the live product ($30k retroactive) and fund the growth that turns it into a sustained source of shielded transactions and new Zcash users ($20k prospective).