Zingo, eZcash, Edge, Zashi, Brave, and Ywallet aren’t competitors
Greetings Zcasher, I am providing a quick update to clarify a few points that seem to be unclear (at least in some contexts).
I’ll be posting a more detailed explanation of how this is true soon, but what’s critical to understand is that no one Zcash App can support the whole Zcash economy, nor should it try. As I have laid out before, we have entered a new era.
There’re more uses for Zcash than can be covered by the existing Apps, and that’s a situation that’s going to become more acute, not less.
Each of the apps I have listed above has a unique:
underlying tech stack
community of developers
set of features
set of use-cases it best serves
If you feel a partisan loyalty to a particular one of these, that might be understandable from an historical perspective, but from a practical perspective it’s roughly analogous to preferring your Signal-App over your Duolingo app. That analogy isn’t perfect, as I will explain in my more detailed post on this topic, but the principle is correct, Zcash needs multiple specialized efficiently interoperating apps.
That last part is key, and is the motivation underlying our work with the Blockchain Commons, Zingo Labs is making this app economy a possibility right now, tomorrow it will be the reality.
What’s the Diff?
Here’s the lightning summary of how these tools have already diverged.
Zingo, Communication
eZcash, Accounting
Edge, Multicoin (Swap?!)
Zashi, Storage/US-Infrastructure-Integration
YWallet, Voting
Brave, web-based
Now wearing my Zingoista Hat, I will say:
Zingo 2.0 is in the works!
By the end of April expect a major new version of Zingo to be available.
That may be the most exciting thing to me about Zcash.
The world is in dire need of a communication protocol that can resist both Sybil and state attacks, and be financially sustainable. Everything out there is fundamentally clunky. Which is fine for birthdays messages and shopping discussions. But it is not, at all, for important matters.
The world needs a communication channel that is rock solid. Zcash can technically do this, today.
Absolutely!! Btw… I have seen many times that it is not recommended to use the same passphrase between wallets. I have always considered this very concerning and unacceptable. Is that still the case?
as someone who has tested the beta messaging on Zingo wallet already in the last beta versions, the message delay is only few seconds so its kinda instant already thanks to the wallet using mempool to find the sent messages (no confirmations needed for messages)
A forest of many apps is being generated that not only build an ecosystem of privacy, but also contribute and enrich styles, ways of seeing this technology, and communication strategies to share their achievements.
At the end of the day, it is an enrichment that we will see in the years to come.
I’m going to guess that you are talking about how long it takes for Zingo to pickup the message whenever the app is running. What happens when the app is not running? That’s where my suggestion to look into the mollysocket method is coming into play.
If indeed using the mempool, isn’t this kind of a hack, that is in essence, a parasistic use of ressources? I would like to make sure this can scale while not unfairly exploiting the hardware ressources of zcash nodes.
yeah dats true. if app is not open im not sure there is a solution yet to see you recieved messages.
to scale to millions messages it wouldnt work probably yes. at lower scale at current time it has no impact on nodes unless this messaging thing gains massive traction.
Alright, that’s what I thought but thanks for clarifying! Obviously, this is only exciting if it scales. Now I can only imagine @zancas has a design that is scaling, so I’m curious to know more.
The notification bit is really key too for adoption imho. People don’t open apps to check if they have messages, it’s a relic thinking of the past. For this to work, I think you need something like the mollysocket where a server that has viewing keys on the account would send a notification on ntfy (or similar).
