What Was the Most Confusing Part of Getting Started With Zano?

[GinoFPM]

Learning how to use a new blockchain can come with questions, whether it involves installing the wallet, synchronizing, staking, sending a transaction, or using an ecosystem application.

What part of getting started with Zano did you find the most confusing?

Share your experience or ask your question below. Your question may also help improve the onboarding experience for future users!

[spazano]

Getting started with Zano was not difficult as I had had experience working with previous crypto. The learning curve began when I first bought some BTC. Getting my head around the blockchain and crypto was a massive challenge for someone who is not technically minded. It required a complete mind shift as I only picked up my first computer in my late 30s. Most people my age look at me with a blank face when I talk about crypto. Even my kids took some convincing to open wallets and still prefer surveillance payment methods e.d. Revolut - due to its convenience and ease of use.

This is the challenge we need to overcome to get more people onboarded - Convenience & ignorance. Most people want it on a plate. At the same time it is necessary to treat everyone as a complete newbie and design with this in mind. Don't assume they know anything - or are at least too lazy to bother to put much effort into learning.

That said, a large part of the attraction of Zano is its ease of use compared to other crypto. The design and functionality of the wallets is excellent and the whole concept of a private ecosystem is very exciting with huge potential. Also there are lots of help pages and a loyal community to seek advice.

Finally it is necessary for people to understand the genuine need for private by default crypto during these times of relentless surveillance. Zano is still greatly underrated in my book but I feel it's only a matter of time.

[kwibs]

For me, it was learning about the different privacy technologies and layers. Many projects claim their transactions are 'private'. But when you look under the hood, the implementations vary widely, and only a handful of projects actually have strong privacy (hidden sender/receiver, amounts, and asset types). Immutability matters too; there are projects out there that promise privacy, but when you read the small text at the bottom, you find there's actually a backdoor for 'authorities'. If we want privacy with a backdoor for some, we might as well just use our regular bank accounts, which work exactly that way.

It's hard to spot the 'real' privacy from the fake, unless you actually learn about the technologies, what they mean, and how they're implemented. This was the biggest learning curve for me at the start.

[tommycat]

All the passwords LOL. I understand the reasoning but had to work out a system to keep track of all different passwords for various functions in Zano. I could have made them all the same but I figured there was a reason for it.

[htzano]

yeah wrapping my head around what a passphrase with secure and unsecure seed actually was was the most confusing for me as i didnt understand the fact that the key stayed the same no mater what.
So no passphrase the key is written out directly. Same wallet, same words, every time.
With a passphrase, the key gets locked in a box first, then written as words. Different passphrase = different looking words. But it's the same key inside.