Code is available so easy enough to tweak the theme & change the name to, errm, maybe āSneakyPidgeonā ? Pidgeons donāt bomb civiliansā¦ well, yes, they do, but it wipes off.
I quite like the āstealthā connection with NightHawk & think that was the intention. Joking aside, a zebra-stripe-theme would be nice.
(EDIT: Not exactly hard, Iām sure the smart people who hang out here can do way better 'cos Iām just goofing around, hereās my attempt)
Well, some people will surely get less enthusiastic about a Zcash wallet which puts a Chinese or a Russian bomber prominently on its front page. Arguments about its coolness, aesthetics and how that particular bomber didnāt harm too many people will sound very different in that case. Exactly the same applies for this particular US bomber in many regions of the world. Weapons are killing devices, talk to a child who lost her family and her legs after a bomber passed over her head and ask her what she thinks about the aesthetics of bombers. Itās absolutely wrong to use weapons as symbols in peaceful projects.
First, this isnāt the only wallet, its not even ECCās wallet. Itās a volunteer effort created by a community member. And they made the choice to go for nighthawk. Itās clever and there are a bunch of cool things about the plane and the aesthetic. Itās not being used because it drops bombs, itās being used because itās stealth and stays off the radar. Thee intent is obvious. That saiid, the fact that it drops bombs and that can be bad ( it can also be good, see stoping genocide in the Balkans), is lost on no one including the authors. Which does raise the issues you allude to, but how important that is is a thing people can reasonably disagree on. Lets not pile on them and lets not derail the thread in which they announce the thing.
Keep in mind that Nighthawk is a project created by a independent group of Zcash enthusiasts, not something released from the ECC or ZFND thereby, it seems a bit rude to badger them about a name they chose because they obviously liked it. They have already gone through the trouble of forking the code, customizing the UI, creating Developer apps accounts for Google and iOS store, secured a Twitter handle, designed the logo, and probably several other things that Iām not thinking of.
If you donāt like the wallet simply because of the name then the code is open-source, you are free to do what they did: Fork it to make it your own.
You have the freedom to use the wallet or not to use the wallet. What else would you like to censor? I think censorship resistance is good. This wallet app is certainly not going to kill anyone.
It means a lot for you to recognize our baby steps. And thank you for choosing the best in class architecture which should make this app future proof for the next couple of years before having to rewrite it again!
Hey @gcsfred1, thanks for the feedback. We agree that it could be made clearer how to send and receive. Weāve since reordered the home screen. Let us know you think!
Hi! Could you add additional protection functionality to Nighthawk?
I mean, Face ID, or password for logging in and making a transaction, as well as one useful function that is available in hardware wallets: a code word, which is essentially a twenty fifth word of recovery phrase and allows you to branch address trees in the wallet and select a desired tree when logging.
I think that this is the last thing that prevents me from abandoning the hardware wallet as a cold wallet in favor of a bundle of Ipod+software wallet. Iām tired of waiting for Z addresses in hardware wallets.
Can you allow users to store the seed in icloud? Some crypto wallets do & it comes in handy.
Sideshift is blocked in some countries. So, having other options to acquire Zcash would be nice. Options doesnāt have to be decentralized exchanges. It could be showing how users can buy Zcash from Gemini (or other trusted exchanges) & transferring to Nighthawk
Single click to go from ETH/BTC to Zcash (via RenZec).
Instant sync? and/or improve zero state experience for first time users.
While Apple iCloud claims strong encryption, they have had security breaches in the past, so Iām unsure if storing the seed in iCloud will be in the best interest of the users. Maybe Iāll review their newer APIs for leveraging iCloud KeyChain which is supposedly more secure?
@NighthawkApps is working to bring an exchange partner to allow more users buy crypto, just need to be careful how we make the integration happen, to preserve the privacy of users till they decide to KYC with a 3rd party.
Iām wary about integrating secondary blockchain protocols in the app in the current stage, and trusting in a 3rd party (ren) to keep the services up, maybe this changes over time.
Yes, initial sync is a pain to watch as a new user, weāre working on ideas like showing āSetting up your walletā status and notifying the user only after background sync is complete.
Donate address should be back under the Profile/Backup button. Weāve had a few micro donations come in along with memos which helps in testing on mainnet and onboarding new devs.
Currently, Nighthawk Wallet for iOS is based straight off ECC codebase and the Android version has some customizations which was possible to maintain for the last 6 months following ZF funding. Now that we have a separate grant for lightwalletd.com setup, we plan to apply to ZOMG for a larger grant to build more features and contribute to upstream ECC codebase and help in resolving the backlog of issues. That way all the developers using Zcash SDKs can benefit.
I think for this you can encrypt the file and allow users to store it on iCloud or any other cloud provider. The user would then only need to make sure that they remember the password to the file. This can be a better option for a lot of people, especially those who use Nighthawk strictly for spending.
Agree, everything is so early let others try it out first before we expose Zcash users to those.
Yes, initial sync is a pain to watch as a new user, weāre working on ideas like showing āSetting up your walletā status and notifying the user only after background sync is complete.
What is the data that needs to be synced for a new wallet? There shouldnāt be any notes received yetā¦
Downloading the latest compact blocks in a privacy-sensitive way ā this depends on network speed & lightwalletd traffic
Scanning and trial decrypting those blocks for shielded transactions related to the wallet ā this takes a while depending on 1) the number of blocks since last scan or wallet height that needs to be processed and 2) the processing power of the mobile device iPhone 7 could take 8x longer than iPhone 10
Processing those related transactions into useful data for the UI ā this is fast
Correct, the sync is done to reduce the future delay in sync for when the user is actually expecting a transaction. Hence the idea of making the syncing happen in the background.
Iām sorry - I still donāt get it. If the user is expecting a transaction, that transaction will happen in the future. So there is no need to download past blocks. Isnāt it what the initial sync is about?
Do you have an opinion on what the best solution is? (I agree that the current situation of having to sync useless block data on first startup is not ideal!)
