Hi! Zingo encourages migration of funds from the transparent pool to Orchard (Sapling to Orchard is also encouraged). I believe this is inline with @joris’s desire to make t-addresses (paraphrase: “2nd class”).
With Zingo, you CAN:
- send to a t-address (the transparent pool)
- receive at a t-address (the transparent pool)
This means that a Zingo User has the OPTION to engage with t-address-using counterparties.
As Far As I Know (AFAIK) this is necessary, if a User wishes to transact with any modern centralized exchange.
With Zingo, you CANNOT:
- send funds from the transparent pool to any counterparty except your own Orchard address
Many people might reasonably object that this policy is overweaning, and it’s not a wallet’s job to dictate User behavior… rather we should simply offer options. In principle, I agree with this… and eventually we may do the work to implement an Advanced setting that allows Users to expose themselves by sending FROM the transparent pool, in a non-Shield transaction.
As currently implemented Zingo, offers a convenient “Path To Privacy” where it receives transparent funds, and then, at the User’s option, migrates those funds to Orchard.
This supports moving value from transparent (and Sapling) into Orchard. We believe that’s an important process.
We believe that maximizing the size of the Shielded pool is critical to Zcash’s value proposition.