Gotcha, just for clarification; a little confused. Are there plans for a new coin in september?
No new coin… just drastically improved!
Any movement of funds from Sprout to Sapling, or vice versa, has to go through the transparent value pool. As far as the protocol is concerned it doesn’t necessarily need to go via a transparent address, but the value must be revealed. This is to support the “turnstile” approach to auditing whether there has been any overall inflation of the monetary base due to protocol flaws - #2248. The user interface to this hasn’t been settled yet because we haven’t implemented the necessary RPC call - #3268. It may involve a separate script that performs the transfer over an extended period to improve privacy.
For future upgrades there might be a way to do monetary base auditing without revealing amounts publically - #2373 - but there are some unsolved technical problems there.
One maybe more for the foundation:
Would it be possible for the foundation to hire external resources for a specific chosen idea beside waiting for the right candidate and idea?
I like some of the grant ideas proposals such as Paynent integration in wechat or whatsapp (if I remember well). Why not having these ideas being voted and ask for a quote from external company to do the work? What about freelance platform such as upwork for example ?
Thanks and as a (hopefully) quick follow up to that, will Sprout transactions be supported following Sapling activation or will it be a case of you must move your shielded funds to Sapling before sending? If Sprout transactions will be allowed how and when will these be phased out?
No strategy for deprecation of transparent address, yet. It’s worth discussing now, though. Maybe we should have a new ticket for this (since I can’t seem to find one). Want to make one??
What are plans(roadmap) for2019 and beyond?
What new features and improvements ZCash is expectedto have in the future ?
It shouldn’t be too hard, but requires some thought and a hard fork if done on chain. You need some flag to signal that this tx is just a vote and not a real spend, and this flag needs to be baked in deep enough to not allow replays with real zec spending, and ideally, not compromise privacy when the zec used to vote is really spent.
One way seems to have a public random string related to the vote issue, and bake this string into the nullifier computation.
#2321 mentioned above is in a different context than stake voting, and doesn’t address the privacy/replay issues I think.
Very special questions.
What is a current status of RnD for zk-smart contracts?
When usersmay expect addition of an execution layerfor Zcash and implementation of zk-executions ?
What are your plans or better to say vision for improvements scalability of ZCash ? Is something on the roadmap re sharding or alternative techs ?
It is recommended to pause sending transactions about an hour before the network upgrade. Here’s a FAQ about that very topic!
This question will have obvious overtones to a well-known coin’s scaling debate.
Could you indicate your position(s) on the ‘natural state’ of Zcash’s blocks given increased demand and usage?
Absent new scaling techniques and irrespective of the existence of an L2, what is the purpose of Zcash’s maximum block size and will it be increased to avoid an artificial ‘fee market’?
That depends a lot on the capabilities of the device. Sapling is primarily designed to support isolation of spend authority in very small devices (in theory a few hundred bytes of RAM, and very little computational power, is sufficient). As the spec says, in that case privacy is lost to whatever party/device is doing the zk-SNARK proving. However, the proving itself is much more efficient in both time and memory for Sapling – so, it’s entirely plausible that a mobile phone or other small/dedicated device can do the whole spending process without loss of privacy to any other party. For that the device wouldn’t necessarily need to be a full node.
We don’t know yet what the timescale will be for support of shielded transactions on mobile.
While someone from the Zcash Foundation is free to answer and may do so, they are a separate entity from the Company and aren’t officially part of this AMA.
The team is heads down on Sapling right now but have plans to update our roadmap post-Sapling once we’ve had more time for deliberations and planning. Stay tuned!
We’re focused on Zcash as a mechanism for Internet money and have not expanded the scope to include smart contracts or Ethereum-like functionality. It would be interesting to see more RnD on this, though. We previously stated an interest in “user issued token” support but have since refocused on improving shielded address functionality and more fundamental usability.
Maybe someone else is interested in doing this to move it along!
Sean Bowe came up with an extremely cool way to do zk-smart contracts called pay to verification key. It’s not gonna be in Sapling and there are no concrete plans on when it will be incorporated. https://github.com/zcash/zcash/issues/2425
There are many possible approaches we’re looking at:
- Succinct blockchains, and similar work by StarkWare
- Block DAG protocols such as SPECTRE and PHANTOM
- Ethereum-style sharding
- I’ve been working in my spare time on an idea that separates the consensus protocol into two layers – a “transaction feed” protocol and a “block consensus” protocol. It’s primarily designed to improve security against 51% attacks but may also help scalability if it works out, and it’s complementary to the succinct blockchain idea.
Initially sprout transactions will be allowed, and my understanding is that there are no concrete plans on how the phasing out will happen.
When can we expect to have official Zcash windows wallet with supportof z-addresses ?