### Terms and Conditions
- [x] I agree to the [Grant Agreement](https://9ba4718…c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471_f81ef4e4b5f040038350270590eb2e42.pdf) terms if funded
- [x] I agree to [Provide KYC information](https://9ba4718c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471_7d9e73d16b584a61bae92282b208efc4.pdf) if funded above $50,000 USD
- [x] I agree to disclose conflicts of interest
- [x] I agree to adhere to the [Code of Conduct](https://forum.zcashcommunity.com/t/zcg-code-of-conduct/41787) and [Communication Guidelines](https://forum.zcashcommunity.com/t/zcg-communication-guidelines/44284)
- [x] I understand all milestone deliverables will be validated and accepted by their intended users or their representatives, who will confirm that the deliverables meet the required quality, functionality, and usability for each user story.
- [x] I agree that for any new open-source software, I will create a `CONTRIBUTING.md` file that reflects the high standards of Zcash development, using the [`librustzcash` style guides](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#styleguides) as a primary reference.
- [x] I understand when contributing to existing Zcash code, I am required to adhere to the project specific contribution guidelines, paying close attention to any [merge](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#merge-workflow), [branch](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#branch-history), [pull request](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#pull-request-review), and [commit](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#commit-messages) guidelines as exemplified in the `librustzcash` repository.
- [x] I agree to post request details on the [Community Forum](https://forum.zcashcommunity.com/c/grants/33)
- [x] I understand it is my responsibility to post a link to this issue on the [Zcash Community Forums](https://forum.zcashcommunity.com/c/grants/33) after this application has been submitted so the community can give input. I understand this is required in order for ZCG to discuss and vote on this grant application.
### Application Owners (@Octocat, @Octocat1)
@kinkin74
### Organization Name
ZECLINK
### How did you learn about Zcash Community Grants
github
### Requested Grant Amount (USD)
40000
### Category
Non-Wallet Applications
### Project Lead
```project-lead.yaml
Name:@kinkin74
Role: Founder & Lead Developer — ZecLink
Background: Founder and lead developer of ZecLink, a web application focused on simplifying Zcash (ZEC) transfers through shareable payment links. Responsible for developing the initial application, implementing Zcash payment functionality, and managing the project's technical infrastructure.
Responsibilities:Lead the development and technical architecture of ZecLink.
Develop and improve Zcash payment-link functionality.
Oversee security, reliability, and transaction recovery improvements.
Maintain the application's infrastructure and development roadmap.
Implement testing and technical documentation.
Manage grant milestones, deliverables, and progress reporting.
```
### Additional Team Members
```team-members.yaml
ZecLink is currently developed and managed by its founder and lead developer, @kinkin74.
External security specialists may be contracted for specific grant milestones, subject to budget and availability.
```
### Project Summary
ZecLink is a Zcash-focused web application that enables users to send and receive ZEC through shareable payment links without requiring the sender to know the recipient's wallet address in advance.
We are requesting $40,000 to improve the application's security, transaction reliability, recovery mechanisms, and usability, supporting broader adoption of Zcash.
### Project Description
ZecLink is a Zcash-focused web application designed to simplify how people send and receive ZEC through secure, shareable payment links.
Our mission is to make Zcash more accessible to everyday users, including people who have little or no experience with cryptocurrencies.
The existing application allows users to select an amount of ZEC, generate a payment link, and fund it directly from their Zcash wallet. Recipients can open the link, verify the available balance and funding status, and initiate a claim to their own Zcash wallet.
This grant proposal seeks to expand ZecLink into a more accessible, reliable, and versatile Zcash payment platform.
### Development Objectives
**1. ZEC-to-USD Bank Cash-Out Integration**
One of our primary objectives is to develop a compliant payment solution that allows a sender to fund a ZecLink with ZEC while the recipient chooses to receive the equivalent value in USD directly into their own eligible US bank account.
The proposed development includes:
- Evaluating regulated payment providers that support Zcash.
- Preparing the necessary business structure and KYB documentation.
- Researching applicable US regulatory and compliance requirements.
- Developing an integration with a suitable payment provider's API.
- Implementing identity-verification and bank-payout workflows.
- Building transaction tracking, fee estimation, and payout-status functionality.
Production availability will depend on legal feasibility, the selected provider's capabilities, and successful onboarding and approval. The grant will initially fund the feasibility assessment and a testable integration prototype.
**2. Native Mobile Applications — iOS and Android**
Develop mobile versions of ZecLink to make Zcash payments more convenient and accessible.
Planned features include payment-link creation, transaction-status monitoring, receiving and claiming functionality, and an intuitive mobile interface.
Our objective is to develop testable mobile applications and prepare them for submission to the Apple App Store and Google Play Store, subject to the relevant platform requirements.
**3. Zcash Wallet Integration**
Improve compatibility with Zcash wallets to simplify funding payment links and receiving ZEC.
The project will evaluate integrations with compatible wallets and supported connection methods, prioritizing user security and interoperability.
**4. Infrastructure, Security, and Reliability**
Improve the technical infrastructure supporting ZecLink, including:
- More reliable server infrastructure.
- Monitoring and operational alerting.
- Backup and recovery procedures.
- Transaction-status verification.
- Improved error handling.
- Security improvements for payment-link credentials.
- Automated testing of critical payment workflows.
Special attention will be given to the handling of interrupted transfers and the limitations of recovering lost payment links.
**5. New Features and User Experience Improvements**
Continue developing ZecLink with additional functionality based on user feedback.
Improvements will focus on reducing friction throughout the payment process, simplifying the interface, and making transaction information easier to understand.
**6. Adoption, Education, and Community Engagement**
Develop educational resources to help new users understand Zcash and link-based payments.
Planned deliverables include:
- Step-by-step tutorials.
- Video demonstrations.
- User onboarding documentation.
- Troubleshooting guides.
- Structured user feedback and usability testing.
- Educational outreach to the Zcash community.
### Expected Impact on the Zcash Ecosystem
ZecLink addresses a practical challenge: sending cryptocurrency to someone who may not already have a wallet or experience using Zcash.
By allowing users to initiate ZEC transfers through links, ZecLink aims to reduce onboarding barriers and make Zcash more convenient for everyday transactions.
Future mobile accessibility, improved wallet interoperability, and the exploration of compliant bank cash-out options could further expand the practical use of ZEC.
### Development and Open-Source Commitment
The project is led by its founder and lead developer, @kinkin74.
Grant-funded development will focus on verifiable technical deliverables, security improvements, interoperability, and user education.
Software developed under the grant will be made publicly available under the MIT license, in accordance with the ZCG Grant Agreement.
The project will provide technical documentation, implementation updates, and milestone reports for community review.
### Funding Scope
**Total Requested Funding: $40,000 USD**
The proposed budget will support:
- Business and regulatory feasibility work.
- KYB preparation and payment-provider integration.
- Mobile application development.
- Zcash wallet interoperability.
- Hosting, infrastructure, and security improvements.
- User education, documentation, and adoption activities.
The grant will be dedicated to developing and improving Zcash-related technology.
Funding will not be used for market making, token liquidity, speculative trading, or promotion of the separate Solana-based $ZLINK token.
### Long-Term Vision
Our long-term vision is to make ZecLink a practical payment solution that connects the simplicity of sharing a link with the capabilities of Zcash.
**Making Zcash easier to send, easier to receive, and more accessible to everyone.**
### Proposed Problem
Despite its strong privacy-focused technology, Zcash still faces significant barriers to everyday adoption, particularly among users who are unfamiliar with cryptocurrency wallets and blockchain transactions.
**1. Complexity of Sending and Receiving ZEC**
Traditional cryptocurrency payments require users to understand wallet addresses, transaction procedures, and wallet compatibility.
For someone new to Zcash, these requirements can make receiving a payment unnecessarily complicated.
There is a need for simpler payment experiences that allow users to send ZEC through familiar methods, such as sharing a link.
**2. Limited Access to Direct Bank Cash-Out**
A major barrier to practical adoption is the difficulty of converting received ZEC into traditional currency.
For example, a person receiving ZEC through a payment link may want to receive its equivalent value in USD directly into their US bank account.
However, this process may require creating an exchange account, completing additional steps, and manually converting and withdrawing funds.
A simplified ZEC-to-USD bank payout experience could make Zcash more useful for payments between individuals.
Implementing such a solution requires a suitable regulated payment provider, identity verification, KYB approval, and compliance with applicable financial regulations.
**3. Limited Mobile Accessibility**
Users increasingly expect financial services to be accessible through mobile applications.
Without dedicated Android and iOS applications, ZecLink cannot offer the complete mobile experience we envision for creating, sharing, and claiming ZEC payment links.
**4. Wallet Integration and User Experience Challenges**
Users may face unnecessary friction when funding payment links or transferring received ZEC into their preferred wallets.
Improved interoperability with compatible Zcash wallets would help simplify these processes and reduce user errors.
**5. Infrastructure, Reliability, and Security**
A payment application must provide reliable transaction monitoring, clear payment-status information, secure handling of claim credentials, and predictable behavior when transactions are delayed or interrupted.
Lost claim links, incomplete operations, and infrastructure interruptions can create uncertainty and potentially put access to funds at risk.
These issues require careful engineering, testing, and clearly documented recovery procedures.
**6. Education and Adoption Barriers**
Many potential users are unfamiliar with Zcash and do not know how to send, receive, or securely manage ZEC.
Accessible tutorials, practical demonstrations, and clear onboarding materials are needed to help users understand and confidently use Zcash-based payment tools.
### Why This Problem Matters
Zcash needs not only strong underlying technology but also practical applications that make its benefits accessible to everyday users.
By addressing payment complexity, wallet interoperability, mobile accessibility, reliability, and the feasibility of compliant bank payouts, ZecLink aims to reduce barriers to Zcash adoption and expand its real-world usefulness.
### Proposed Solution
ZecLink proposes to simplify Zcash payments by expanding its existing web application into a more accessible, reliable, and versatile payment platform.
The project builds on an initial working implementation of shareable ZEC payment links and an existing, temporarily disabled Cash Out integration.
With $40,000 in funding from Zcash Community Grants, we aim to improve the existing application and develop the following capabilities.
**1. Complete and Enable the Existing ZEC-to-Fiat Cash Out Integration**
ZecLink has already integrated an initial automated conversion flow designed to support:
**ZEC → USDC → Fiat → Bank Account**
This functionality is currently disabled while further development, testing, provider compatibility, and operational requirements are addressed.
Our objective is to make it possible for a sender to fund a ZecLink payment link with ZEC and for the recipient to choose to receive the equivalent value in USD in their own eligible US bank account.
Grant-funded development will focus on:
- Reviewing and improving the existing conversion integration.
- Validating ZEC-to-USDC conversion and the subsequent fiat payout process.
- Evaluating payment providers and their support for third-party-funded transactions.
- Preparing the required business structure and KYB documentation.
- Implementing recipient identity verification through an appropriate provider.
- Improving exchange-rate quotations, fee transparency, and payout-status tracking.
- Testing failed transactions, interrupted conversions, refunds, and recovery procedures.
- Completing security and compliance assessments before any production activation.
The existing integration provides a technical starting point, but live bank payouts will remain conditional on the necessary provider approvals, regulatory requirements, and successful testing.
**2. Develop ZecLink Mobile Applications for Android and iOS**
We plan to develop mobile versions of ZecLink to make Zcash payment links easier to create, share, and claim from smartphones.
The mobile applications will focus on:
- Creating ZEC payment links.
- Checking payment and funding status.
- Claiming received ZEC.
- Supporting eligible Cash Out workflows when available.
- Providing a simple and accessible user interface.
Our goal is to deliver testable mobile applications and prepare them for publication through Google Play and the Apple App Store, subject to platform requirements.
**3. Improve Zcash Wallet Integration**
We will improve interoperability with compatible Zcash wallets to simplify funding and receiving transactions.
This includes evaluating supported wallet connection methods, reducing unnecessary steps, improving transaction feedback, and strengthening compatibility testing.
**4. Improve Security, Infrastructure, and Reliability**
We will strengthen ZecLink's technical infrastructure through:
- More reliable server hosting and monitoring.
- Improved Zcash transaction-status tracking.
- Secure handling of payment-link credentials.
- Automated testing of payment and claim workflows.
- Better error handling and operational recovery procedures.
- Improved backup, logging, and diagnostic capabilities.
Special attention will be given to interrupted transactions, failed claims, and recovery limitations.
**5. Introduce New Features and Improve User Experience**
We will continue developing functionality that makes ZEC payments easier and safer for everyday users.
Development priorities will include clearer transaction information, improved payment flows, better usability, and additional features informed by user feedback.
**6. Promote Zcash Adoption Through Education**
We will develop practical educational materials explaining how to use ZecLink and how Zcash payments work.
Deliverables will include:
- Step-by-step user guides.
- Video demonstrations.
- Mobile onboarding documentation.
- Troubleshooting resources.
- Community testing and feedback collection.
### Expected Deliverables
The proposed grant will support:
- An improved ZecLink web application.
- A tested and documented version of the existing ZEC → USDC → fiat Cash Out integration, with production activation subject to external approvals.
- Testable Android and iOS mobile applications.
- Improved Zcash wallet interoperability.
- More reliable infrastructure and transaction processing.
- Expanded automated tests and security documentation.
- Educational resources for Zcash users.
- Publicly available grant-funded software under the MIT license.
### Expected Impact
ZecLink will make Zcash easier to send and receive by reducing the technical complexity associated with traditional cryptocurrency transfers.
By combining payment links, improved wallet compatibility, mobile accessibility, and a pathway toward bank-account payouts, the project aims to increase the everyday usefulness and adoption of ZEC.
The $40,000 grant will accelerate the development of an existing Zcash application rather than fund an entirely new project from scratch.
### Solution Format
**Project Type:** Open-source Zcash payment application, available through a web platform and planned mobile applications for Android and iOS.
**Existing Product:** https://zeclink.io/
ZecLink is an existing web application that enables users to send and receive ZEC through shareable payment links.
The proposed grant will support the development and improvement of the following components:
**1. Web Application**
- Improved payment-link creation, funding, and claiming workflows.
- New features and user experience improvements.
- More reliable transaction monitoring and error handling.
**2. Cash Out Integration**
- Further development of the existing, temporarily disabled ZEC → USDC → fiat conversion integration.
- Payment-provider API integration and testing.
- Recipient identity-verification and bank-payout workflows.
- Clear exchange-rate, fee, and payout-status information.
- Documented procedures for failed or interrupted conversions.
Production activation will depend on technical validation, regulatory feasibility, and provider approval.
**3. Mobile Applications**
- Testable Android application.
- Testable iOS application.
- Mobile payment-link creation, transaction monitoring, and claiming functionality.
- Preparation for publication on Google Play and the Apple App Store.
**4. Zcash Wallet Interoperability**
- Improved compatibility with supported Zcash wallets.
- Simplified link-funding and receiving workflows.
- Integration tests and technical documentation.
**5. Infrastructure and Security**
- Improved hosting infrastructure and monitoring.
- Automated testing of critical payment flows.
- Better handling of transaction failures and recovery scenarios.
- Security documentation and operational safeguards.
**6. Educational Resources**
- User guides and onboarding documentation.
- Video demonstrations and tutorials.
- Troubleshooting resources.
- Community testing and feedback collection.
### Delivery Format
Grant-funded deliverables will include software source code, testable application builds, technical documentation, automated tests, user guides, and milestone progress reports.
Grant-funded software components will be published under the MIT license in accordance with ZCG requirements.
Development progress and completed deliverables will be made available for community review.
### Dependencies
ZecLink is an existing Zcash payment-link application. The proposed development will build on its current infrastructure and functionality while introducing additional integrations and capabilities.
The project has the following dependencies:
**1. Zcash Network and Wallet Infrastructure**
ZecLink depends on reliable Zcash mainnet and testnet connectivity, compatible software libraries, and supported wallet interfaces.
Further development will focus on transaction monitoring, payment-link funding, claiming, and improved interoperability with Zcash wallets.
**2. Cash Out Conversion and Payment Providers**
ZecLink has an initial Cash Out integration that follows the intended conversion flow:
**ZEC → USDC → Fiat → Bank Account**
This functionality is currently disabled pending further development and validation.
Production activation will depend on the availability and approval of suitable providers supporting the required conversion steps, US bank payouts, and payments to verified recipients who may differ from the original ZEC sender.
Dependencies include provider APIs, transaction-processing capabilities, identity-verification services, fee quotations, and payout-status reporting.
**3. Business Registration, KYB, and Regulatory Compliance**
Enabling bank payouts will require an appropriate legal and operational structure, business verification (KYB), recipient identity verification (KYC), and assessment of applicable US financial regulations.
The preferred company jurisdiction and payment provider will be selected based on verified operational and compliance requirements.
**4. Mobile Application Development**
The planned Android and iOS applications will depend on suitable mobile development frameworks, testing environments, and developer accounts.
Distribution through Google Play and the Apple App Store will depend on compliance with their applicable policies and review processes.
**5. Hosting and Technical Infrastructure**
ZecLink requires reliable server hosting, secure infrastructure configuration, network connectivity, transaction monitoring, backup procedures, and operational maintenance.
The grant will support improvements to the reliability and security of these services.
**6. Security and External Technical Services**
Certain aspects of development may require external expertise, including security review, payment integration assistance, and legal or compliance consultation.
**7. Community Feedback and Testing**
Usability testing and feedback from Zcash community members will help validate the application's improvements and guide documentation and onboarding development.
### Dependency Risk Management
The existing Zcash payment-link functionality can be improved independently of the proposed banking integration.
If a suitable Cash Out provider cannot be approved during the grant period, the project will focus on completing the documented integration architecture, technical prototype, testing, and compliance feasibility assessment rather than activating unapproved financial services.
Progress and dependency-related limitations will be reported transparently as part of the grant milestones.
### Technical Approach
ZecLink will build upon its existing web application, extending its architecture to support improved Zcash payment links, enhanced wallet interoperability, mobile applications, and a compliant bank Cash Out integration.
Development will be organized into independent, testable components to reduce technical risks and allow progress even when third-party integrations require additional approvals.
**1. Zcash Payment-Link Infrastructure**
We will improve the existing payment-link creation, funding, verification, and claiming workflows.
Development will focus on:
- Reliable Zcash transaction and confirmation monitoring.
- Secure generation and handling of payment-link credentials.
- Prevention of duplicate or unauthorized claims.
- Better handling of delayed, interrupted, and failed transactions.
- Automated tests covering critical payment flows.
- Clear recovery procedures, where technically feasible.
The application will continue supporting direct ZEC claims independently of the proposed bank payout functionality.
**2. Existing Cash Out Integration: ZEC → USDC → Fiat**
ZecLink already includes an initial automated Cash Out integration designed around the following conversion sequence:
**ZEC → USDC → Fiat → Bank Account**
This functionality is currently disabled and requires further testing, provider validation, and operational review.
Our intended user experience is:
1. A sender creates and funds a ZecLink payment link with ZEC.
2. The recipient opens the link and selects the bank Cash Out option.
3. The recipient completes identity verification through an approved financial services provider.
4. The system requests a conversion quotation, including applicable rates and fees.
5. Following recipient authorization, the supported conversion process exchanges ZEC for USDC and subsequently converts the value into USD.
6. An approved payout provider processes the transfer to the recipient's own eligible US bank account.
7. ZecLink displays the transaction status and final outcome.
The grant-funded work will include reviewing the existing integration, improving API handling, validating provider compatibility, and implementing reliable transaction tracking.
We will also develop safeguards against duplicate claims, conversion failures, expired quotations, rejected payouts, and interrupted operations.
Production activation will require confirmation that the participating providers accept the complete transaction model, including payments where the original ZEC sender and bank payout recipient are different people.
Business verification (KYB), recipient identity verification (KYC), and applicable regulatory requirements will be addressed before activation.
**3. Android and iOS Mobile Development**
We plan to develop mobile applications that reuse appropriate parts of the existing ZecLink architecture.
The initial mobile versions will prioritize:
- Creating and sharing ZEC payment links.
- Viewing funding and transaction status.
- Claiming ZEC through supported workflows.
- Displaying clear payment instructions and transaction feedback.
- Accessing Cash Out functionality only when the relevant integrations are approved and available.
Development will include mobile interface design, functional testing, security testing, and preparation for app store submission.
**4. Zcash Wallet Integration**
We will evaluate and implement supported wallet interoperability methods to simplify ZEC funding and claiming.
Development will prioritize compatibility, secure transaction handling, and minimizing unnecessary steps for users.
Wallet integrations will be tested against their documented capabilities rather than assuming universal support.
**5. Infrastructure, Reliability, and Security**
We will improve the application's hosting and operational infrastructure through:
- Reliable server deployment and configuration.
- Application monitoring and operational alerts.
- Secure management of infrastructure secrets.
- Backup and restoration procedures.
- Improved transaction-status synchronization.
- Error logging that avoids exposing sensitive claim credentials.
- Automated tests and deployment validation.
Security work will also examine how claim credentials and transaction states are managed throughout the payment lifecycle.
**6. Testing and Quality Assurance**
Development will use Zcash testnet where appropriate, along with isolated test environments and available provider sandbox APIs.
Testing will cover successful transactions, invalid inputs, interrupted payment flows, duplicate claim attempts, API failures, and recovery scenarios.
Mainnet functionality will be tested carefully with appropriate safeguards before any production release.
**7. Open-Source Development and Documentation**
Grant-funded software will be published under the MIT license in accordance with ZCG requirements.
Deliverables will include relevant source code, technical documentation, automated tests, deployment instructions, user guides, and a CONTRIBUTING.md file.
Development milestones will be supported by demonstrable software improvements and publicly documented progress.
### Implementation Strategy
The work will proceed incrementally, prioritizing the reliability and security of existing Zcash payment functionality before introducing additional operational dependencies.
The Cash Out integration, mobile applications, wallet interoperability improvements, and infrastructure work will have separately verifiable deliverables.
If banking integration approvals are delayed or unavailable, the project will still deliver documented technical work, a testable prototype where supported, and improvements to the core Zcash application.
Our goal is to deliver practical, verifiable improvements that make Zcash easier to send, receive, and use in everyday payment scenarios.
### Upstream Merge Opportunities
ZecLink is an independent application built around the Zcash ecosystem. The proposed grant will focus primarily on improving ZecLink's existing functionality and developing new capabilities for Zcash users.
The project does not require modifications to the Zcash consensus protocol or core network rules.
However, development may produce reusable components and improvements that could benefit other projects within the Zcash ecosystem.
Potential upstream contribution opportunities include:
- Improvements to Zcash wallet interoperability and transaction-handling components.
- Reusable utilities for payment-link creation, funding verification, and transaction-status monitoring.
- Automated tests and documentation related to Zcash payment workflows.
- Bug fixes or compatibility improvements discovered in open-source dependencies.
- Technical documentation that may help other developers integrate Zcash payments into their applications.
Where relevant, we will evaluate submitting pull requests to the appropriate upstream repositories and coordinate with their maintainers.
Grant-funded ZecLink components will be published under the MIT license, allowing other developers to inspect, reuse, and build upon the work.
No upstream merge is guaranteed or assumed. Any contributions will depend on technical relevance, compatibility with upstream licenses, and acceptance by the respective maintainers.
Our goal is to create useful open-source software that supports both ZecLink's development and the broader Zcash ecosystem.
### Open Source License
MIT
### Hardware/Software Costs (USD)
3000
### Hardware/Software Justification
**Total: $3,000 USD**
The requested hardware and software budget will support the development, testing, deployment, and maintenance of ZecLink throughout the grant period.
**1. Server Hosting and Infrastructure — $1,200**
Reliable hosting for the ZecLink web application, backend services, Zcash network connectivity, and development environments.
**2. Development and Testing Tools — $600**
Software tools, testing environments, and developer resources required for web and mobile application development.
**3. Monitoring, Backups, and Security Tools — $700**
Infrastructure monitoring, operational alerts, backup storage, secure configuration management, and tools for diagnosing application issues.
**4. Mobile Application Testing and Deployment — $500**
Testing infrastructure, mobile development resources, and applicable developer account fees for preparing Android and iOS applications.
### Expected Outcome
These resources will improve the reliability, security, and maintainability of ZecLink while supporting the development of new features, wallet integrations, mobile applications, and the proposed Cash Out functionality.
All costs are estimates and will be documented during grant execution.
### Service Costs (USD)
12000
### Service Costs Justification
**Total Requested: $12,000 USD**
The service budget will cover specialized external services required to develop, validate, and prepare ZecLink's expanded payment functionality.
**1. US Legal and Regulatory Compliance Consultation — $4,000**
Professional consultation to assess the regulatory requirements associated with the proposed ZEC-to-USD bank payout functionality.
This includes evaluating the legal structure, applicable US financial regulations, third-party payment flows, and compliance responsibilities.
**2. Business Verification (KYB) and Payment Provider Onboarding — $2,000**
Support for preparing business verification documentation, evaluating payment providers, and completing the technical and operational onboarding requirements.
ZecLink already has an initial, temporarily disabled Cash Out integration based on the following conversion flow:
**ZEC → USDC → Fiat → Bank Account**
The objective is to validate and advance this integration using an appropriate payment provider.
Business registration and onboarding expenses will be incurred only where necessary, eligible under the grant, and permitted by the relevant providers.
**3. External Security Review — $3,000**
A scoped security review of critical ZecLink components, including payment-link credentials, transaction handling, Cash Out integration points, and potential vulnerabilities.
The scope of the review will be prioritized according to available funding and technical risk.
**4. Payment Integration and Technical Consulting — $2,000**
Specialized technical assistance with payment APIs, conversion workflows, transaction-status monitoring, and handling failed or interrupted payout operations.
**5. Usability Testing and Educational Production Services — $1,000**
External assistance with usability testing, user documentation, educational materials, and video tutorials focused on Zcash adoption.
### Expected Outcomes
The service budget will support:
- A documented legal and compliance feasibility assessment.
- Payment-provider evaluation and KYB preparation.
- Technical validation of the existing Cash Out integration.
- An external security review of selected critical components.
- Improved technical documentation and educational resources.
All amounts are preliminary estimates. Services will be procured according to project needs, provider availability, and applicable grant requirements.
Production Cash Out activation is conditional on successful technical validation, regulatory feasibility, and approval by the relevant financial service providers.
### Compensation Costs (USD)
25000
### Compensation Costs Justification
**Total Requested: $25,000 USD**
The compensation budget will fund the development work performed by ZecLink's founder and lead developer, @kinkin74.
The project lead will be responsible for software engineering, technical architecture, implementation, testing, deployment, documentation, and milestone delivery.
The proposed compensation is based on an estimated **500 development hours at $50 per hour** over the grant period.
**1. ZecLink Web Application Development — $5,000 (100 hours)**
Improve the existing payment-link creation, funding, claiming, transaction monitoring, and user experience workflows.
**2. Cash Out Integration Development — $6,000 (120 hours)**
Improve and test the existing, temporarily disabled ZEC → USDC → fiat conversion integration.
Implement provider API workflows, payment-status tracking, fee and exchange-rate presentation, and error-handling mechanisms.
Production activation will depend on provider approval and regulatory feasibility.
**3. Android and iOS Mobile Development — $7,000 (140 hours)**
Develop testable mobile applications with core ZecLink payment-link functionality, transaction-status monitoring, and supported claiming workflows.
Prepare mobile builds and technical documentation for potential app store submission.
**4. Zcash Wallet Integration — $3,000 (60 hours)**
Improve compatibility with supported Zcash wallets, funding methods, and transaction workflows.
**5. Infrastructure, Testing, and Security Improvements — $2,500 (50 hours)**
Improve server deployment, monitoring, transaction reliability, error handling, security controls, and automated testing.
**6. Documentation, Community Feedback, and Grant Reporting — $1,500 (30 hours)**
Prepare technical documentation, development updates, milestone reports, and materials supporting community testing.
### Compensation Summary
- Project Lead: @kinkin74
- Role: Founder & Lead Developer
- Estimated Work: 500 hours
- Proposed Hourly Rate: $50 USD
- Total Compensation: $25,000 USD
Compensation will be tied to documented development activities and verifiable milestone deliverables.
The proposed work will focus exclusively on Zcash-related application development and will not fund activities associated with the separate Solana-based $ZLINK token.
### Total Budget (USD)
40000
### Previous Funding
No
### Previous Funding Details
ZecLink has not received any previous grants or external funding.
The project has been entirely self-funded by its founder and lead developer, @kinkin74.
### Other Funding Sources
No
### Other Funding Sources Details
ZecLink currently has no confirmed external funding sources.
### Implementation Risks
ZecLink is an existing Zcash payment-link application. The proposed grant will support improvements to its current functionality and the development of additional capabilities.
We have identified the following implementation risks and mitigation strategies.
**1. Cash Out Provider Compatibility and Regulatory Approval**
ZecLink has an initial, temporarily disabled Cash Out integration based on the following conversion flow:
**ZEC → USDC → Fiat → Bank Account**
A major risk is that payment providers may not support all required operations, including Zcash transactions, automated conversion, and USD payouts to US bank accounts belonging to recipients who differ from the original senders.
Business verification (KYB), recipient identity verification (KYC), and applicable US regulatory requirements may also delay or prevent production activation.
**Mitigation:** Evaluate provider capabilities and compliance requirements before production deployment. Consult appropriate legal and compliance specialists, validate the existing integration, and build a testable prototype. Live bank payouts will only be enabled after the necessary approvals and technical validation.
**2. Security of Payment Links and Claim Credentials**
Payment links may involve sensitive claim credentials. Lost, exposed, or incorrectly handled credentials could result in unauthorized access or loss of access to funds.
**Mitigation:** Review credential generation and handling, minimize exposure of sensitive information, improve transaction validation, implement appropriate safeguards against duplicate claims, and document recovery limitations.
**3. Transaction Failures and Conversion Errors**
Network delays, API failures, expired exchange quotations, or interrupted conversion operations could affect transaction processing.
**Mitigation:** Implement reliable transaction-state tracking, authenticated provider callbacks, error handling, retry safeguards, and documented procedures for failed or incomplete operations.
**4. Mobile Application Development and Store Approval**
Developing Android and iOS applications may require additional platform-specific engineering. App store reviews and cryptocurrency-related policies may delay publication.
**Mitigation:** Prioritize testable mobile application builds with essential ZecLink functionality. Validate platform requirements during development and treat public store approval as dependent on external review.
**5. Zcash Wallet Compatibility**
Different Zcash wallets may support different address types, transaction methods, and integration capabilities.
**Mitigation:** Evaluate documented wallet capabilities, prioritize supported integration methods, and perform compatibility testing before release.
**6. Infrastructure Reliability and Availability**
Hosting failures, connectivity issues, or interruptions to Zcash network services could reduce application availability or delay payment-status updates.
**Mitigation:** Improve hosting reliability, monitoring, backups, operational alerts, deployment procedures, and incident recovery documentation.
**7. Project Scope and Resource Constraints**
The proposed work includes several technical areas, including Cash Out, mobile applications, wallet integration, infrastructure, and education. Delivering all objectives within a $40,000 budget requires careful prioritization.
**Mitigation:** Divide development into measurable milestones, prioritize core Zcash functionality, limit the initial scope of mobile and Cash Out integrations, and report progress transparently.
### Risk Management Commitment
Project progress will be reviewed against documented milestones and acceptance criteria.
Dependencies outside the project's control, particularly regulatory approval, payment-provider onboarding, and app store approval, will not be presented as guaranteed outcomes.
If a third-party dependency prevents production deployment, the project will document the limitation and deliver the agreed technical work, tests, and feasibility findings for community review, subject to ZCG approval of the relevant milestone criteria.
### Potential Side Effects
The proposed development of ZecLink aims to improve accessibility and usability within the Zcash ecosystem. However, introducing new payment capabilities may create unintended consequences that must be carefully managed.
**1. Privacy Considerations**
The proposed Cash Out functionality involves converting ZEC into USDC and subsequently into fiat currency through external financial service providers.
This process may require identity verification and may expose transaction-related information to third-party providers.
**Mitigation:** Clearly inform users about the privacy implications of using Cash Out. Keep direct ZEC-to-ZEC transfers available as a separate option and minimize the collection and retention of personal information.
**2. Financial and Transaction Risks**
Exchange-rate fluctuations, conversion fees, network delays, and failed bank payouts could affect the final amount received by users.
**Mitigation:** Display available exchange rates, estimated fees, and expected payout amounts before confirmation. Implement transaction-status tracking and procedures for handling unsuccessful operations.
**3. Security Risks**
Additional integrations and mobile applications may increase the application's potential attack surface.
Unauthorized access to payment-link credentials or weaknesses in third-party APIs could put funds at risk.
**Mitigation:** Strengthen credential handling, access controls, testing, monitoring, and security reviews before releasing new functionality.
**4. Dependency on External Providers**
Cash Out services may become temporarily unavailable because of provider outages, regulatory changes, or changes in supported assets and regions.
**Mitigation:** Keep core ZEC payment-link functionality independent of banking integrations and communicate external service limitations clearly.
**5. User Confusion and Payment Errors**
Users unfamiliar with cryptocurrencies may misunderstand the difference between receiving ZEC and receiving USD through a regulated financial provider.
**Mitigation:** Provide clear explanations, payment confirmations, transparent fees, and educational materials. Make the distinction between direct ZEC transfers and fiat payouts easy to understand.
**6. Infrastructure and Operational Impact**
Increased application usage may create additional server load, maintenance requirements, and operational costs.
**Mitigation:** Improve infrastructure monitoring, deployment practices, backup procedures, and resource management as usage grows.
### Overall Approach
ZecLink will prioritize user security, transparent payment processes, privacy awareness, and reliable operation.
The project will not activate financial integrations until the necessary technical, operational, and compliance requirements have been satisfied.
Any significant risks or limitations identified during development will be documented and communicated through project updates and milestone reports.
### Success Metrics
The success of the ZecLink grant will be measured through verifiable software deliverables, technical improvements, testing results, and community adoption activities.
**1. Zcash Payment-Link Improvements**
- Deliver an updated version of the ZecLink web application.
- Improve payment-link creation, funding verification, and ZEC claiming workflows.
- Implement automated tests covering successful transactions, invalid inputs, interrupted operations, and duplicate claim attempts.
- Document security practices and known recovery limitations.
**Success Criteria:** Demonstrate working payment-link workflows in a test environment, publish relevant test results, and document the completed improvements.
**2. Cash Out Integration Development**
- Review and improve the existing, temporarily disabled ZEC → USDC → fiat integration.
- Document the complete technical architecture and dependencies.
- Evaluate at least two potential payment or conversion providers.
- Document US regulatory feasibility and business KYB requirements.
- Develop and demonstrate a testable Cash Out integration prototype, using sandbox APIs or simulations where necessary.
- Implement transaction-state tracking, fee presentation, and failure-handling procedures.
**Success Criteria:** Provide technical documentation, provider evaluation results, and a demonstrated integration prototype. Production activation will depend on provider approval and applicable regulatory requirements.
**3. Android and iOS Applications**
- Develop one testable Android application build.
- Develop one testable iOS application build.
- Support core ZecLink features, including payment-link creation, funding-status monitoring, and supported claiming workflows.
- Conduct functional testing and document the results.
**Success Criteria:** Provide demonstrable mobile builds and testing documentation. Public app store publication will remain subject to platform approval.
**4. Zcash Wallet Interoperability**
- Evaluate at least two compatible Zcash wallets or integration methods.
- Implement at least one improved wallet interaction workflow, subject to documented wallet capabilities.
- Test link funding and ZEC claiming with the supported integration methods.
**Success Criteria:** Demonstrate the supported integration, publish compatibility notes, and document test results.
**5. Infrastructure, Reliability, and Security**
- Implement application monitoring and operational alerts.
- Document backup and restoration procedures.
- Improve transaction-status handling and operational error reporting.
- Complete automated testing of critical workflows.
- Commission a scoped external security review and document remediation of identified issues within the agreed scope.
**Success Criteria:** Provide evidence of deployed improvements, operational documentation, automated test results, and security review findings or an appropriate review summary.
**6. Education and Community Adoption**
- Publish at least three user guides or tutorials.
- Produce at least two video demonstrations.
- Conduct at least one structured community testing and feedback round.
- Publish a summary of feedback received and improvements made.
**Success Criteria:** Make educational materials publicly accessible and provide documented community-testing results.
**7. Open-Source Deliverables and Reporting**
- Publish grant-funded software components under the MIT license.
- Provide technical documentation and a CONTRIBUTING.md file.
- Publish milestone progress updates and demonstrations.
- Provide a final report summarizing completed deliverables, limitations, and future development priorities.
### Overall Success Criteria
The project will be considered successful when the agreed grant-funded software improvements, mobile prototypes, Cash Out feasibility and integration work, wallet interoperability enhancements, infrastructure improvements, and educational materials have been delivered and demonstrated.
External approvals, including payment-provider onboarding, regulatory authorization, and app store approval, will be tracked separately and will not be represented as guaranteed outcomes.
### Startup Funding (USD)
5000
### Startup Funding Justification
**Requested Startup Funding: $5,000 USD**
The initial funding will support the preparation and early implementation activities required to begin the proposed ZecLink development work.
ZecLink is already an existing, self-funded application, and the startup funding will be used to establish the technical and operational foundation for the grant milestones.
**Planned Allocation:**
- **$1,500 — Infrastructure and Development Environment:** Server improvements, development environments, monitoring, backups, and testing resources.
- **$1,500 — Cash Out Feasibility and Provider Evaluation:** Initial technical and compliance assessment of the existing, temporarily disabled ZEC → USDC → fiat integration, including requirements for USD payouts to US bank accounts.
- **$1,000 — Mobile Development Preparation:** Android and iOS development environments, application architecture, and initial user interface work.
- **$1,000 — Core Application Development:** Initial improvements to Zcash payment-link reliability, testing, and technical documentation.
**Expected Outcomes:**
The startup phase will establish the infrastructure, technical specifications, provider evaluation plan, and development environments necessary for the subsequent milestones.
All startup expenditures will be documented, and the resulting technical work will support the grant's verifiable deliverables.
The startup funding is included within the total requested grant amount of $40,000 USD and is not an additional request.
### Milestone Details
```milestones.yaml
- **Milestone: 1 — Zcash Core Improvements and Wallet Integration**
**Amount (USD):** 8000
**Expected Completion Date:** 2027-01-15
**User Stories:**
- As a Zcash sender, I want to create and fund a payment link reliably, so that I can send ZEC without knowing the recipient's wallet address in advance.
- As a Zcash recipient, I want to claim my funds securely, so that I can receive ZEC in my own wallet.
- As a wallet user, I want clearer funding and claiming instructions, so that I can complete transfers with fewer errors.
**Deliverables:**
- Improved payment-link creation, funding verification, and claiming workflows.
- Improved transaction monitoring and error handling.
- Evaluation of at least two Zcash wallets or wallet integration methods.
- At least one demonstrated wallet interoperability improvement.
- Automated tests covering critical payment-link functionality.
- Technical documentation and MIT-licensed grant-funded source code.
**Acceptance Criteria:**
- Users can demonstrate creating, funding, and claiming payment links in a controlled testing environment.
- The supported wallet integration is demonstrated and documented.
- Automated tests cover successful and failed transaction scenarios.
- Source code, documentation, and test results are available for community review.
- **Milestone: 2 — Cash Out Integration and KYB Preparation**
**Amount (USD):** 10000
**Expected Completion Date:** 2027-03-01
**User Stories:**
- As a ZecLink recipient, I want the option to receive the value of a ZEC payment link in USD in my own eligible US bank account, so that I can use the payment without manually converting cryptocurrency.
- As a recipient, I want to see conversion rates, fees, and payout status, so that I understand the amount I may receive.
- As a payment operator, I want a documented and compliant integration architecture, so that Cash Out can be evaluated for safe production activation.
**Deliverables:**
- Technical review and improvement of the existing, temporarily disabled ZEC → USDC → fiat integration.
- Documented conversion and bank-payout architecture.
- Evaluation of at least two potential payment or conversion providers.
- US regulatory feasibility assessment and KYB preparation documentation.
- A testable Cash Out prototype using sandbox APIs or clearly identified simulations where supported.
- Conversion quotation, payout-status tracking, error-handling, and recovery workflow documentation.
**Acceptance Criteria:**
- The existing Cash Out integration has been reviewed and its limitations documented.
- At least two providers or integration approaches have been evaluated against ZEC support, recipient identity verification, and US bank payout requirements.
- A Cash Out workflow can be demonstrated in a test environment or through clearly identified simulations.
- Failed and interrupted payment scenarios are covered by test cases.
- Compliance dependencies and production activation requirements are documented.
- Production bank payouts remain disabled until suitable provider approvals and legal requirements are satisfied.
- **Milestone: 3 — Android and iOS Mobile Applications**
**Amount (USD):** 9000
**Expected Completion Date:** 2027-04-15
**User Stories:**
- As a mobile user, I want to create and share ZEC payment links from my smartphone, so that I can send Zcash conveniently.
- As a recipient, I want to check a payment link and claim ZEC through a mobile-friendly interface, so that I do not need a desktop computer.
- As a new Zcash user, I want simple instructions and clear transaction feedback, so that I can use the application with confidence.
**Deliverables:**
- Testable Android application build.
- Testable iOS application build.
- Mobile interfaces for payment-link creation and sharing.
- Funding-status monitoring and supported ZEC claiming workflows.
- Mobile usability improvements and functional testing.
- Documentation for installation, testing, and future app store submission.
**Acceptance Criteria:**
- Android and iOS builds can be installed and demonstrated on supported test devices or test environments.
- Core payment-link features can be demonstrated on both platforms.
- Functional testing results and known limitations are documented.
- Grant-funded source code and mobile development documentation are available for community review.
- Public app store approval remains subject to external review and is not a guaranteed milestone outcome.
- **Milestone: 4 — Security, Infrastructure, Education and Final Delivery**
**Amount (USD):** 8000
**Expected Completion Date:** 2027-05-31
**User Stories:**
- As a ZecLink user, I want reliable transaction updates and clear error messages, so that I can understand the status of my funds.
- As a new Zcash user, I want accessible tutorials, so that I can learn how to send and receive ZEC safely.
- As a Zcash community developer, I want access to documented open-source components, so that I can review and potentially reuse the grant-funded work.
**Deliverables:**
- Improved server monitoring, operational alerts, and backup procedures.
- Additional security testing and a scoped external security review.
- Documentation of critical findings and remediation actions within the agreed scope.
- At least three public user guides or tutorials.
- At least two video demonstrations.
- At least one structured community testing and feedback round.
- Published MIT-licensed grant-funded source code, technical documentation, and CONTRIBUTING.md.
- Final milestone report and project demonstration.
**Acceptance Criteria:**
- Infrastructure monitoring and documented recovery procedures are demonstrated.
- The scoped security review is completed and an appropriate findings summary is available.
- Educational materials are publicly accessible.
- Community testing feedback and resulting improvements are documented.
- Grant-funded source code, documentation, and final deliverables are available for community review.
- A final report identifies completed functionality, remaining limitations, and future development priorities.
### Supporting Documents
```files.yaml
Project Website:
https://zeclink.io
```