Fortifying Osmosis Blockchain Through Real-time Alerts and Advanced Threat Detection

Fortifying Osmosis through real-time alerts and advanced threat detection

Strengthening Zcash privacy: real-time threat detection, enhanced transaction security, and resilience against evolving risks.

Applicant name: Cyvers.ai
Team member name: Deddy Lavid (CEO) Meir Dolev (CTO)

Our team brings a wealth of experience to the table. With a CEO boasting a decade in AI and ML startup management, including a successful acquisition, and a CTO holding seven years in product and tech roles, we possess a robust background. Our expertise spans AI, machine learning, cybersecurity, and blockchain, with a proven track record in transforming abstract ideas into thriving startups. We’ve demonstrated our skills in managing large-scale projects, ensuring their success and contributing valuable innovations to the tech landscape

Our project addresses the pressing issue of privacy and security within the Zcash ecosystem. As a privacy-focused blockchain, Zcash faces challenges such as potential vulnerabilities, transaction security concerns, and the need for real-time threat detection. Our solution aims to add substantial value by:

  1. Enhancing Transaction Security:
    Strengthening Zcash’s privacy by fortifying transactional security against potential threats and vulnerabilities.

  2. Real-time Threat Detection:
    Providing a cutting-edge security layer with real-time threat detection capabilities to actively monitor and respond to emerging risks.

  3. Resilience Against Evolving Threats:
    Fortifying the Zcash ecosystem against evolving cybersecurity threats, ensuring the continued integrity of transactions and user privacy.

  4. User Confidence and Trust:
    Building user confidence by actively addressing privacy and security concerns, encouraging broader adoption of Zcash for secure transactions.

  5. Long-term Ecosystem Health:
    Contributing to the long-term health and resilience of the Zcash ecosystem by implementing robust security measures that adapt to changing threat landscapes.

In summary, our project not only solves immediate privacy and security challenges but also positions Zcash as a more resilient and secure blockchain, fostering trust among users and contributing to the sustained growth of the ecosystem.

Proposed Solution:

At a high level, our proposed solution involves the implementation of advanced security measures tailored for the Zcash ecosystem. Key components of our solution include:

  1. Transaction Security Enhancement:
    Implementing robust security protocols to enhance the privacy and security of Zcash transactions, safeguarding them against potential vulnerabilities.

  2. Real-time Threat Detection System:
    Developing a cutting-edge security layer with real-time threat detection capabilities. This system actively monitors the Zcash network for suspicious activity and triggers timely responses to mitigate potential risks.

  3. Privacy-Focused Security Measures:
    Tailoring security measures to align with the privacy-centric nature of Zcash. This includes addressing specific challenges related to shielded transactions and ensuring that security enhancements complement and reinforce Zcash’s privacy features.

  4. Adaptive Security Protocols:
    Creating adaptive security protocols that evolve with the changing threat landscape. This ensures that Zcash remains resilient against emerging cybersecurity challenges over time.

  5. User-Friendly Integration:
    Ensuring that our security solution seamlessly integrates into the Zcash ecosystem without compromising user experience. The goal is to provide enhanced security without causing disruptions to the existing functionality of the blockchain.

In essence, our solution is designed to fortify Zcash’s privacy and security infrastructure, providing users with a secure environment for conducting transactions while actively mitigating potential threats in real-time. The focus is on creating a comprehensive security framework that aligns with the unique characteristics of the Zcash blockchain.

Solution Format:

The final deliverable will be a fully integrated and operational security layer designed specifically for the Zcash ecosystem. This solution will consist of:

  1. Security Protocols Implementation:
    Executing and integrating advanced security protocols to fortify the Zcash blockchain against potential vulnerabilities and threats.

  2. Real-time Threat Detection System:
    Developing and deploying a real-time threat detection system that actively monitors the Zcash network for suspicious activities and triggers alerts for timely response.

  3. Adaptive Security Measures:
    Implementing adaptive security measures that evolve with the dynamic threat landscape, ensuring ongoing protection against emerging cybersecurity risks.

  4. Privacy-Focused Enhancements:
    Tailoring security enhancements to align with the privacy-centric nature of Zcash, specifically addressing challenges related to shielded transactions.

  5. User Interface for Monitoring:
    Providing a user-friendly interface for monitoring security metrics and threat alerts, enabling users and network administrators to stay informed about the security status of the Zcash blockchain.

  6. Documentation and Training Materials:
    Preparing comprehensive documentation and training materials to facilitate the seamless integration of the security layer into the Zcash ecosystem. This includes user guides, technical documentation, and any necessary training resources.

The deliverable will be a comprehensive, operational, and user-friendly security solution that adds significant value to the Zcash ecosystem, enhancing transactional privacy, security, and resilience against evolving threats

Technical Approach:

  1. Security Protocol Implementation:
    Approach: Develop and implement robust security protocols to fortify the Zcash blockchain.
    Components: Encryption algorithms, cryptographic protocols, and integrity verification mechanisms.
    Workflow: Integrate security protocols seamlessly into the Zcash network.

  2. Real-time Threat Detection System:
    Approach: Implement a machine learning-driven threat detection system.
    Components: Data collectors, anomaly detection models, and alert generation mechanisms.
    Workflow: Continuously monitor Zcash transactions, analyze patterns, and trigger alerts in real-time for suspicious activities.

  3. Adaptive Security Measures:
    Approach: Utilize machine learning for adaptive security.
    Components: Learning models, continuous monitoring algorithms, and dynamic threat response mechanisms.
    Workflow: Train models on historical data, adapt to new threats, and dynamically adjust security measures.

  4. Privacy-Focused Enhancements:
    Approach: Address privacy challenges associated with shielded transactions.
    Components: Privacy-preserving algorithms, secure key management, and transaction obfuscation techniques.
    Workflow: Enhance privacy features without compromising security, ensuring compatibility with Zcash’s privacy goals.

  5. User Interface for Monitoring:
    Approach: Develop an intuitive interface for users and administrators.
    Components: Graphical dashboards, real-time data feeds, and alert management tools.
    Workflow: Provide a user-friendly interface for monitoring security metrics, receiving alerts, and responding to potential threats.

  6. Documentation and Training Materials:
    Approach: Create comprehensive documentation and training resources.
    Components: User guides, technical documentation, and interactive training materials.
    Workflow: Facilitate the smooth integration of the security layer by providing clear instructions and educational resources.

Workflow Diagram:

Zcash Blockchain
|
v

Security Protocols
|
v

Threat Detection System
|
v

Adaptive Security Measures
|
v

Privacy-Focused Enhancements
|
v

User Interface Monitoring Tools

This technical approach integrates advanced security measures seamlessly into the Zcash ecosystem, leveraging machine learning, privacy-preserving techniques, and user-friendly interfaces to ensure a comprehensive and effective security solution.

Dependencies:

  1. Zcash Foundation (ZF)
    Involvement Required: Collaboration for seamless integration of security measures into the Zcash protocol.
    Dependencies: Access to Zcash network data, coordination for protocol adjustments, and feedback on the compatibility of our solution with the existing Zcash infrastructure.

  2. Zcash Community:
    Involvement Required: Community engagement and feedback.
    Dependencies: Support and feedback from the Zcash community to ensure that the security solution aligns with user expectations and addresses specific community concerns.

  3. Third-Party Validators:
    Involvement Required: Validation of security protocols.
    Dependencies: Collaboration with external entities for the validation and verification of implemented security protocols to ensure industry-standard compliance.

  4. Security Auditors:
    Involvement Required: External security audits.
    Dependencies: Collaboration with independent security auditors to conduct thorough assessments and audits of the implemented security measures to identify and address potential vulnerabilities.

  5. Regulatory Bodies (if applicable):
    Involvement Required: Compliance checks.
    Dependencies: Collaboration to ensure that the security solution aligns with regulatory requirements and standards if applicable in the jurisdictions where Zcash operates.

Incorporation for Usability:
For our work to be fully usable, ZF, and other external organizations would need to incorporate our implemented security protocols into the Zcash protocol. This involves acceptance, integration, and coordination to ensure that the security enhancements seamlessly become part of the standard Zcash infrastructure.

The success of our project relies on collaborative efforts with ZF, and the broader Zcash community to integrate our security measures effectively and ensure a secure and privacy-focused Zcash ecosystem.

Execution risks:

  1. Protocol Compatibility:
    Obstacle: Ensuring seamless integration with the Zcash protocol.
    Risk: Incompatibility issues could arise, requiring close collaboration with ZF, ECC, and the Zcash community to address and resolve.

  2. Community Acceptance:
    Obstacle: Gaining acceptance and support from the Zcash community.
    Risk: If the community is not on board, adoption could be hindered. Continuous community engagement and feedback are crucial to mitigate this risk.

  3. Regulatory Compliance:
    Obstacle: Ensuring compliance with evolving regulatory standards.
    Risk: Changes in regulations could impact the usability and acceptance of our solution. Regular consultation with regulatory bodies is essential to adapt to any new requirements.

  4. External Audits:
    Obstacle: Conducting thorough external security audits.
    Risk: Identifying and addressing all potential vulnerabilities may be challenging. Collaboration with reputable security auditors is vital to ensure a robust assessment.

  5. Evolving Threat Landscape:
    Obstacle: Keeping up with emerging cybersecurity threats.
    Risk: If the security measures become outdated, the system could be vulnerable. Regular updates and collaboration with security experts are necessary to stay ahead of evolving threats.

  6. Dependency on External Entities:
    Obstacle: Dependence on ZF, ECC, and external validators.
    Risk: Delays or resistance from external entities could impact project timelines. Ongoing communication and collaboration are critical to mitigate this risk.

  7. Privacy and Usability Trade-offs:
    Obstacle: Balancing enhanced security with user-friendly features.
    Risk: Introducing security measures that compromise user experience could hinder adoption. Striking the right balance is essential, requiring user feedback and iterative improvements.

  8. Unknown Factors:
    Obstacle: Unforeseen challenges and factors.
    Risk: Unexpected developments, such as major changes in the blockchain landscape or technology, could pose challenges. Maintaining adaptability and flexibility is crucial to navigate unknown factors.

Incorporation for Usability:
To be fully usable, our work must be incorporated into the Zcash protocol by ZF, ECC, and other relevant stakeholders. Any resistance or delays in this process could impede the successful implementation of our security enhancements. Ongoing collaboration and coordination are essential to ensure a smooth integration process.

Unintended Consequences:

  1. Usability Impact:
    Risk: Overemphasis on security could potentially impact the user-friendly nature of the Zcash ecosystem, leading to a less intuitive experience for users.
    Mitigation: Continuous user feedback and iterative design improvements to strike the right balance between security and usability.

  2. Privacy Implications:
    Risk: Introducing new privacy measures may inadvertently impact user privacy in unintended ways.
    Mitigation: Rigorous testing and privacy impact assessments to ensure that security measures align with Zcash’s privacy-centric goals without compromising user anonymity.

  3. Interoperability Challenges:
    Risk: Changes to the Zcash protocol could introduce interoperability challenges with other blockchain networks.
    Mitigation: Close collaboration with ZF, ECC, and industry standards to ensure compatibility and interoperability with other blockchain ecosystems.

  4. Technical Debt Accumulation:
    Risk: Rapid implementation without careful consideration may lead to technical debt, complicating future development efforts.
    Mitigation: Adherence to best practices, continuous code reviews, and a commitment to addressing technical debt as part of ongoing development cycles.

  5. Centralization Concerns:
    Risk: Unintended consequences could contribute to centralization concerns, impacting the decentralized nature of the Zcash network.
    Mitigation: Regular assessments and adjustments to minimize centralization risks, ensuring that the security enhancements align with the principles of decentralization.

  6. Increased Complexity:
    Risk: Adding security layers may increase the overall complexity of the Zcash protocol, potentially affecting stability.
    Mitigation: Incremental implementation and thorough testing to identify and address any stability issues introduced by the security measures.

  7. Education Gaps:
    Risk: Users may face challenges in understanding and adapting to new security features, leading to potential misuse or frustration.
    Mitigation: Comprehensive educational materials, tutorials, and community outreach to bridge knowledge gaps and facilitate user understanding.

  8. Dependency on External Entities:
    Risk: Increased dependence on external validators and security auditors may introduce reliance on specific entities, potentially affecting decentralization.
    Mitigation: Diversification of external partnerships and clear communication about the role of external entities in the project.

  9. Elevated Compliance Burden:
    Risk: Introducing additional security measures may elevate the compliance burden on users and stakeholders.
    Mitigation: Proactive engagement with regulatory bodies to align security measures with regulatory standards, and clear communication about compliance requirements.

It is crucial to proactively identify and address potential unintended consequences, utilizing a combination of thoughtful design, thorough testing, continuous community engagement, and agile development practices to ensure the success of the project without compromising key aspects of the Zcash ecosystem.

Evaluation plan:

Quantitative Metrics:

  1. Threat Detection Accuracy:
    Metric: Percentage of accurately detected threats in real-time.
    Measurement: Continuous monitoring and auditing of threat detection algorithms.

  2. User Adoption Rate:
    Metric: Percentage increase in user adoption of the enhanced security features.
    Measurement: Regular analysis of user engagement and adoption statistics.

  3. Transaction Privacy Enhancement:
    Metric: Improvement in the privacy of shielded transactions.
    Measurement: Comparative analysis of the privacy features of shielded transactions before and after implementation.

  4. Response Time to Threats:
    Metric: Average time taken to respond to identified threats.
    Measurement: Real-time monitoring and analysis of response times.

  5. System Stability:
    Metric: Reduction in system downtime and stability issues.
    Measurement: Ongoing monitoring of system performance and incident reports.

  6. Community Feedback:
    Metric: Positive community sentiment regarding the security enhancements.
    Measurement: Regular surveys, forums, and feedback channels to gauge community satisfaction.

  7. External Security Audits:
    Metric: Positive outcomes from external security audits.
    Measurement: Results and feedback from independent security auditors.

Qualitative Metrics:

  1. User Experience (UX) Assessment:
    Metric: User feedback on the usability and intuitiveness of the security features.
    Measurement: User surveys, interviews, and UX testing sessions.

  2. Community Engagement:
    Metric: Active participation and discussions within the Zcash community.
    Measurement: Tracking community forums, discussions, and involvement in project-related activities.

  3. Regulatory Compliance Adherence:
    Metric: Successful alignment with regulatory standards.
    Measurement: Regular updates on compliance status and engagements with regulatory bodies.

  4. Privacy Preservation Feedback:
    Metric: User feedback on the effectiveness and impact of privacy enhancements.
    Measurement: Surveys and feedback sessions focused on privacy-related features.

  5. Education and Training Effectiveness:
    Metric: User understanding and proficiency in utilizing the security features.
    Measurement: Assessment of educational materials’ effectiveness and user competence through training sessions.

  6. Collaboration with External Entities:
    Metric: Positive collaboration and feedback from external validators and auditors.
    Measurement: Documentation of collaborative efforts and feedback from external partners.

Reporting Schedule:

  1. Regular community updates through blog posts, newsletters, and dedicated communication channels.

  2. Quarterly reports detailing quantitative metrics and summarizing qualitative assessments.
    Annual comprehensive reports showcasing the overall impact and achievements of the security enhancement project.

The evaluation plan aims to provide a holistic view of the project’s success, combining both quantitative and qualitative metrics to ensure transparency and accountability to the Zcash community.

Hardware/Software total budget:
$50000.00 USD

Budget Justification: $50,000

  1. Hardware Infrastructure (30%):
    Purpose: Procurement of specialized hardware for running intensive threat detection algorithms and maintaining a robust analytical engine.
    Justification: Advanced hardware is essential for achieving real-time threat detection and maintaining the high-performance requirements of the security system. This includes servers, storage solutions, and specialized hardware accelerators for efficient processing.

  2. Software Development and Integration (40%):
    Purpose: Allocation for software development, integration, and modification to adapt the existing security solution for seamless integration into the Zcash protocol.
    Justification: Significant resources are needed for the modification of existing security algorithms, development of new features specific to Zcash, and integration with the Zcash protocol. This includes coding, testing, and adapting the solution to ensure compatibility and effectiveness within the Zcash ecosystem.

  3. Security Audits and Validation (20%):
    Purpose: Budget allocation for engaging external security auditors and validators to ensure the robustness and effectiveness of the implemented security measures.
    Justification: External validation is critical to identify vulnerabilities and weaknesses that might not be apparent during internal testing. The cost includes fees for reputable security audit firms and professionals to conduct thorough assessments.

  4. Educational Resources and Community Outreach (10%):
    Purpose: Provision for creating educational materials, conducting training sessions, and community outreach to ensure users understand and utilize the enhanced security features effectively.
    Justification: User education is crucial for the successful adoption and implementation of new security features. This budget includes the creation of tutorials, documentation, and outreach programs to engage and educate the Zcash community.

Summary: The budget of $50,000 is strategically distributed to cover the key components required for the successful implementation of the security enhancement project. It ensures that we have the necessary hardware infrastructure, resources for software development and integration, external validation through security audits, and a dedicated effort for user education and community engagement. This budget allocation is aimed at delivering a comprehensive and effective security solution tailored to the specific needs of the Zcash ecosystem.

Services total budget (cloud, hosting, etc.):
$25000.00 USD

Services Budget Justification: $25,000

  1. Cloud Services (60%):
    Purpose: Subscription to cloud services for hosting, scaling, and ensuring the availability and performance of the security system.
    Justification: Cloud services provide the flexibility and scalability required for hosting the analytical engine and handling varying workloads. This budget covers expenses associated with cloud infrastructure, data storage, and computational resources.

  2. Maintenance and Monitoring Tools (25%):
    Purpose: Investment in tools and services for continuous monitoring, maintenance, and optimization of the hosted security infrastructure.
    Justification: Ongoing monitoring is crucial for identifying potential issues, ensuring system stability, and optimizing resource utilization. This budget includes subscriptions to monitoring tools and services for proactive maintenance.

  3. Backup and Redundancy Measures (15%):
    Purpose: Implementation of backup and redundancy measures to enhance system reliability and minimize downtime.
    Justification: Redundancy is essential for ensuring continuous operation in the event of failures or unexpected incidents. This budget covers expenses related to backup solutions, redundancy configurations, and failover mechanisms.

Summary: The services budget of $25,000 is allocated to cover the essential aspects of cloud services, maintenance tools, and backup measures. Cloud services form the core of the budget, ensuring the necessary infrastructure for hosting and scaling the security system. Additionally, investments in maintenance and monitoring tools, along with backup and redundancy measures, contribute to the overall reliability and resilience of the hosted solution. This budget allocation aligns with the requirements for a robust and well-maintained cloud-based infrastructure.

Compensation total budget:
$25000.00 USD

Compensation Budget Justification: $25,000

  1. Security Experts and Engineers (70%):
    Purpose: Compensation for skilled security experts and engineers responsible for the development, modification, and integration of security features into the Zcash ecosystem.
    Justification: Attracting and retaining top-tier security professionals is essential for the success of the project. This budget allocation ensures competitive compensation to build and maintain a highly skilled team capable of addressing the unique security challenges of the Zcash ecosystem.

  2. Educational and Outreach Specialists (20%):
    Purpose: Compensation for specialists responsible for creating educational materials, conducting training sessions, and engaging in community outreach to promote user understanding of enhanced security features.
    Justification: Effective communication and education are vital for user adoption and success. This budget supports specialists dedicated to creating educational content, hosting training sessions, and fostering community engagement.

  3. Project Management and Coordination (10%):
    Purpose: Compensation for project managers and coordinators overseeing the entire project lifecycle, ensuring smooth collaboration, timely deliverables, and effective communication.
    Justification: Project management is critical for the success of complex projects. This budget allocation covers compensation for professionals experienced in project coordination, stakeholder management, and ensuring adherence to timelines and milestones.

Summary: The compensation budget of $25,000 is strategically allocated to attract and retain a highly skilled team of security experts, engineers, educational specialists, and project managers. Competitive compensation is crucial for building a dedicated and motivated team capable of successfully implementing and managing the security enhancement project within the Zcash ecosystem. This budget prioritizes human capital as a key driver of project success and sustainability

Milestone 1 - estimated completion date: 01/31/2024 - $50,000.00
Deliverable 1.1

Blockchain Integration:

Objective: Establishing a robust foundation for CyVers.ai within the Zcash Blockchain by deploying and maintaining nodes as primary data sources for the CyVers Security Operations Center (SOC) analytical engine.

Execution Steps:

  • Node Deployment and Maintenance (15 days, 500 hours): Deploy and maintain nodes strategically positioned for optimal data collection. Ensure continuous operation and synchronization with the Zcash Blockchain.

  • Transactional and Smart Contract Data Retrieval Services (15 days, 500 hours): Develop services dedicated to retrieving transactional data. Implement services for retrieving smart contract data, ensuring a comprehensive dataset for analysis.

  • Parser Implementation and Network Data Enrichment (10 days, 300 hours): Implement parsers to extract and structure network data. Enrich network data to provide contextual depth for subsequent analysis.

  • Feature Extraction for ML Models (5 days, 200 hours): Extract required features necessary for the development of machine learning models. Ensure seamless integration with the CyVers SOC analytical engine.

Completion Criteria: Blockchain data seamlessly flows from nodes through the ETL process, ready for machine learning model integration.

Duration: 45 days Team: 4 members Budget: $50,000 USD.

Milestone 2 - estimated completion date: 02/03/2024 - $25000.00
Deliverable 2.1

Attack Detection Engine: Objective: Develop and deploy an attack detection engine customized for Zcash, incorporating advanced machine learning models.

Execution Steps:

  • Research and Dataset Building (20 days, 600 hours): Conduct research to identify malicious contracts and potential attacks. Build datasets specific to Zcash to inform the training of machine learning models.

  • ML Model Development (25 days, 800 hours): Build ML models addressing the Preparation Phase of attacks, including malicious funding and contract deployments. Develop a behavioral analysis model for detecting access control/private key leakage attacks.

  • Risk Engine and Model (10 days, 400 hours): Construct a risk engine for the classification of attacks. Develop a risk scoring mechanism for transactions and interactions.

  • Model Deployment (5 days, 200 hours): Deploy ML models and risk engine within the Zcash Blockchain environment.

Completion Criteria: Real-time alerts are generated for transactions based on advanced ML models.

Duration: 60 days Team: 6 members Budget: $25,000 USD.

Milestone 3 - estimated completion date: 12/30/2023 - $25000.00
Deliverable 3.1

Alerting and Response Engine: Objective: Implement a responsive alerting and automated response system to enhance real-time threat mitigation within the Zcash ecosystem.

Execution Steps:

  • Alerting Mechanism (15 days, 500 hours): Implement alerting mechanisms through various channels like Slack, Discord, email, and Telegram.

  • Automated Response Implementation (10 days, 400 hours): Develop automated responses for fund transfers from wallets/contracts to customer backup wallets. Implement automated responses to pause contracts based on threat analysis.

Completion Criteria: Actions triggered by the analytical engine are executed as defined in real-time scenarios.

The project timeline was determined through a meticulous planning process that considered various factors to ensure realistic and achievable milestones. The key considerations in determining the project timeline include:

  1. Task Complexity: The complexity of each task, such as node deployment, data retrieval, machine learning model development, and system deployment, was carefully assessed. More intricate tasks were allocated a proportionate amount of time to ensure thorough execution.

  2. Resource Availability: The availability of skilled team members and their working hours influenced the timeline. The allocation of tasks was designed to make the best use of team members’ expertise and time.

  3. Sequential Dependencies: Tasks were organized based on dependencies, ensuring that certain activities could only commence once their predecessors were completed. This sequential arrangement contributed to a logical flow of activities.

  4. Parallel Execution: Where possible, tasks with minimal dependencies were scheduled to run concurrently, optimizing efficiency and reducing overall project duration.

  5. Realistic Work Estimates: The duration of each task was estimated based on a realistic assessment of the time required for successful completion. This involved considering potential challenges and unforeseen circumstances.

  6. Review and Iteration: The timeline was subject to thorough review and iterative adjustments to account for any changes in project scope, emerging requirements, or unforeseen challenges.

  7. Stakeholder Expectations: The expectations of stakeholders, including the grant provider and the project team, were considered to align the timeline with their objectives and deadlines.

In summary, the project timeline was a result of a comprehensive analysis that balanced task complexity, resource availability, dependencies, and stakeholder expectations to create a realistic and achievable roadmap for the successful implementation of the security project within the Zcash ecosystem.

Please let us know if there are any questions. We look forward to hearing your valuable feedback and thoughts.

Here’s the link to the proposal on the grants platform:

Hi @cyvers - Welcome to the forum, and thank you for submitting your grant proposal! We will review it in the upcoming weeks and reach out if we have any questions.

In the meantime, if you have any questions for us, you can post them to this thread or DM us at @ZcashGrants.

Zcash Community - We want to hear your feedback on this grant! You can post your comments to this thread or DM us at @ZcashGrants if you’d like to provide feedback in private.

Thanks!

@cyvers Thank you for your submission. After consideration from @ZcashGrants and sufficient time for the community to provide feedback on the forum, the committee has decided to reject this proposal.

The committee appreciates your grant submission efforts and encourages you to continue as an active member of the Zcash community going forward, both here on the forum and in the below avenues as well:

1 Like