Title:
Nighthawk Wallet Maintenance and Self-Funding Improvements
Applicant name:
Nighthawk Apps
Team member name:
Aditya Bharadwaj
Team member name:
Matthew Watt
Team member name:
Mandeep Bhalothia
Team member name:
Dmytrii Gonchar
Pitch: A one-liner elevator pitch version of your proposal
1 Year Nighthawk Wallet Maintenance and Self-Funding Improvements
Total Request (USD):
$180000.00 USD
Have you previously received a grant from Zcash Community Grants (formerly called ZOMG) or ZF?
Yes
Please provide details:
Nighthawk Apps has been working on developing the updated Nighthawk Wallet & Public Infrastructure
Are you seeking or have you received funding from other sources for this proposed project?
No
Applicant background:
We are Nighthawk Apps, the creators of Nighthawk Wallet and public goods for the Zcash ecosystem - lightwallted.com and ZcashBlockExplorer.com
The Wallet developers’ backgrounds are as follows:
Matthew Watt https://www.linkedin.com/in/matthewgwatt/
Mandeep Bhalothia https://www.linkedin.com/in/mandeepbhalothia/
Dmytrii Gonchar https://www.linkedin.com/in/dgonchar/
Description of Problem or Opportunity:
As a Zcash-focused native wallet for Android and iOS platforms, Nighthawk must remain updated with the evolving mobile ecosystem and deliver exceptional end-user support. This proposal aims to fund one year of maintenance, app updates, and user support/help, ensuring the continued success and satisfaction of our users.
Additionally, we propose to build a self-funding feature that will allow Nighthawk users to fund its developers by tipping a part of the transaction amount(customizable).
Last year, we successfully delivered several app updates, fixes, and new developments without any external funding:
-
Released 9 app updates with bug fixes on both Android and iOS platforms.
-
Conducted a prototype and user study involving Zcash-based currencies, including ZEC, DECIZEC, CENTZ, MILLIZEC, ZED, and MICROZatoshi.
-
Implemented the integration of Unstoppable Domains support.
-
Enabled translations from contributors by setting up CrowdIn.
-
Added support for Android 13 and iOS 16.
-
Published the iOS app on the Mac App Store, allowing it to be used on ARM-based computers.
-
Implemented a secure PDF wallet backup feature for Android users.
-
Provided comprehensive end-user support through public channels (such as Twitter) and private channels (such as email and z2z).
This year, our team has undergone a thorough onboarding process for native app developers and kickstarted development, focusing on revamping wallets in accordance with our roadmap. Funding these items will ensure continuous development and support for the wallet apps even after the release of the final milestone.
Proposed Solution: Describe the solution at a high level.
A) 1 Year Maintenance of Nighthawk Wallet covering (but not limited to):
-
Support updated Zcash Protocol / Network Rules
-
Support for Android 15 & iOS 18 platforms (mid-2024)
-
Minor Improvements e.g. Dynamic Island on iOS, SideShift deep integration in the wallet
-
Responding to audit reports and fixes, if necessary
-
User Support on Twitter and Email
-
Bug-fixes
-
App updates
It does not encompass substantial modifications to the SDK, except for bug fixes through pull requests, nor does it include the development of new features such as support for a new pool, ZSAs, or Shielded Swaps.
B) Utilize ZIP-321 to allow users to show their support for the wallet developers by providing an option to make a payment as a tip when conducting outgoing fund transfers.
The funding will be contingent upon the successful release of Nighthawk Wallet’s final milestone by September 2023.
Solution Format: What is the exact form of the final deliverable you’re creating?
We will provide monthly updates on the forum, addressing bug fixes and implementing additional improvements, following the monthly cadence established in 2022.
Technical Approach: Dive into the how of your project. Describe your approaches, components, workflows, methodology, etc. Bullet points and diagrams are appreciated!
A combination of native Android development in Kotlin and native iOS development in Swift.
Dependencies: What external entities is your project dependent on? What involvement is required from ZF, ECC, and/or other external organizations? Who would have to incorporate your work in order for it to be usable?
Any required custom modifications to the SDK will be integrated by forking the ECC Mobile SDKs, thereby reducing dependency.
Execution risks: What obstacles do you expect? What is most likely to go wrong? Which unknown factors could jeopardize success? Who would have to incorporate your work in order for it to be usable?
To avoid the potential challenges of publishing on US-based stores and potential regulatory policies impacting crypto wallets, we can ensure the ongoing availability of our work through the F-Droid Store.