Hey folks! Zingo supports Unified Addresses.
If a user opts to send to a t-address the transaction will be partially public.
If a user chooses to offer a t-address the transaction will be partially, or depending on the sender, wholly public.
We can add warnings to make it more explicit to the user that this is the case, but what if a user wants to leak data?
We aren’t interested in working to proscribe behavior. In other words, we want to offer people innovative new options, not dictate to them what they should do.
Philosophically we are motivated by the idea that tech should serve the user not dictate to them.
Zingo incentivizes its users to want to use shielded transactions. This is because our technology is focused on, and building on, encrypted memo fields that only exist in shielded transactions.
We believe that this will align users interests in a way that naturally expands the shielded transaction set.
I will try an analogy…
Suppose that you think that riding horses is problematic because horses poop in the street. People riding hoverboards have to dodge and weave around horse-poop all the time.
What should you do? Launch an anti-horse campaign? Maybe horses should be shot on sight? Maybe horse-riders should be publicly derided for their anti-social behavior?
Or maybe, we should build better hoverboards that float above the poop?
I don’t think legacy t-addresses are worth bothering with. People will stop riding horses when alternatives are better. We’re building systems that offer new features to folks using shielded addresses. We believe that those features will be attractive enough to convince people to use them (and hence stop using t-addresses), at least most of the time.
On the other hand if the occasional horse-back ride is appropriate, then folks can choose that option.
I predict that the expansion in shielded transactions that comes from users making self-aware choices will make t-addresses a minor fraction of the total transaction pool in the near future.
In other words, the solution is to provide superior alternatives, not to dictate-via-tech how people should be private.
ZingoLabs will be publishing a Grant Proposal to the @ZcashGrants committee soon. That proposal will outline the specific features we plan, that will, among other things render this issue increasingly obsolete.
Not to put too fine a point on it, if you want the transaction pool to shift away from t-addresses, then support Zingo we’re innovating in ways that will causes that to happen.