Quote from: coinmancan on June 05, 2018, 12:53:43 AM

Quote from: tearodactyl on June 04, 2018, 10:54:17 PM

Quote from: coinmancan on June 04, 2018, 05:11:09 PM

(Just read through all of the arguing. Good. That's why this forum is better than Discord. I've seen people get banned in Discord for simple things like just disagreeing to larger things like posting facts. Keep steering people to Bitcointalk everyone!)

Just installed the ZERO wallet... there is no password feature, anywhere? No "Encrypt Wallet" feature? Nothing in the text menu. Am I missing something? This doesn't seem very secure at all.

As an example to test things, like in other wallets, I created a new receiving address. In other wallets a password is required to do so. No password dialog popped up.

And I wrote it elsewhere, however writing again. The next wallet update needs some help. Examples would be animations on the splash screen so it doesn't appear frozen and removing the large green bar after the wallet is synced.

coinmancan, thanks for detailed feedback!

First, let me address the security question. We are distributing not only a desktop wallet but also a full node running the blockchain behind it. This is like a Qt wallet in the Bitcoin domain, and architecturally is different from a mobile (SVP) wallet that uses a full node running remotely. In a very real sense, securing the entire computer is needed. This includes physical security of the unit and the room, strong password for the OS login, prompt screen lock with a password, perhaps even a secured BIOS.

Much appreciate the UX observations, and do keep them coming. Would like some comparisons of features and UX, between this and other desktop wallets, like Bitcoin-style Qt, Swing, etc. And in addition to critique, an occasional word of praise would be so welcome.
Tearo

Would be happy to oblige on the praise as it is important! (and thank you for your reply above.)

The wallet is VERY slick. Good job Color scheme well-done. The graphic choice and placement is perfect.

I have multiple machines online 24/7 running 5+ different QT wallets/nodes. All, I repeat, *all* have passwords that are required to send, spend, create new addresses, etc. It may be overkill as yes, the PC needs to be secure from viruses and malware as well as the basic security parameters like you mentioned. (Which are VERY important by the way!) It was just shocking as I've worked on more than a dozen node wallets and have never seen one with no password functionality. And on a privacy coin at that.

I can see that there was a high price of $12 when everything in crypto had skyrocketed. I'm sure those who bought at that time are not happy, but hey, Bitcoin was $20K too, so everything went down. The depressed price is not necessarily a sign of the product-- it's a sign of the market.

Keep up the good work and I look forward to investing in and learning more about your project.

Thank you for the feedback. The basic problem with wallet encryption as it stands today is that the function is disabled at the node level, and I believe this is so for Zcash and all of the Zcash forks (Hush, Zencash, Z-Classic, etc...). The issue appears to revolve around the z-addresses not functioning properly when the wallet.dat (or wallet.zero in our case) is encrypted. More research is required to unravel this issue. If I'm mistaken on this point and somebody has figured it out please let me know.

In the meantime for end user functionality I've been researching some methods to encrypt/decrypt the wallet file or folder when in use using methods external to the node, but I haven't really worked out a full solution yet.

Which Qt wallet are you running? My personal experience with them has been a little different as they have not required a password in their basic setup.
CryptoForge