What’s your Zcash Thesis?

[BrunchTime]

This is so awesome! And just the beginning

[JKDC]

@JKDC

I think Gemini said they would support Z addresses in the future when they added Zcash. ECC should see how close they are to supporting them and if not what they need to support them. That would be a very big step in the right direction. Coinbase and Binance would then feel pressure to do the same.

@joshs

We are working with the Gemini team on various things and have a great relationship with them. But I’m not at liberty to discuss any specifics beyond what they’ve stated publicly.

But what about this?

[joshs]

One step at a time. Today was a big one.

[sarang]

Is it known why they chose not to support shielded transactions, instead of only shielding and deshielding? If so, can you say why?

[joshs]

I don’t know that I can. What I think I can say is that today’s news is part of a multi-step plan that we started some time back and that sending to a zaddr was implemented as soon as it was feasible. Sorry to be coy and light on detail. I believe the support announced today is a big deal and we shouldn’t underestimate its significance.

[sarang]

Can you say if their current unwillingness to add shielded support is due to technical limitations (e.g. multisignature support) or perceived regulatory risk?

[joshs]

I don’t believe they’ve said anything about an “unwillingness.” I’m also not aware of any perceived regulatory risk. You might ask them in the Twitter Q&A tomorrow. We will also soon announce another livestream focused on regulation and privacy that you might be interested in. Stay tuned.

[sarang]

Fair enough. At any rate, I’m very curious as to why they only support shielding and deshielding, and not shielded. Any insight would be appreciated.

[sarang]

Is there a way to ensure this question is asked without asking it myself at the Twitter event? I am not on Twitter and have absolutely no desire to join.

[BrunchTime]

It’ll get asked. If nobody else does, I will

[sarang]

Awesome, thank you!