I understand Zcon3 consumed a ton of energy from the core ECC, ZCG, and ZF staffers (and I personally want to acknowledge: That is the best set of media we’ve ever received to the Zcash ecosystem. Ever), but this is a thread to ask the general question.
What is up Next? To my understanding we’re the tribes wondering in the desert from the old testament.
Is the work to transition to Proof of Stake the next big milestone on the schedule?
Have we got interim product deliveries of interest?
Do we anticipate that the Posterity Fund debate and deployment will happen sooner than PoS?
I hope PoS and the Posterity Fund are not going to eclipse development on recursion, more efficient trial decryption, faster sync for lightwallets, faster verification for zcashd, general greater efficiency, better wallets, better UX…
Great additional topics and they’re exactly what I hope this thread can shine light on.
What sort of priority and-or timelines do your list of items have?
Now that you mentioned it I think the implementation of Recursively Proofed ZKPs is probably next up for delivery (I recall an ECC engineer mentioning that Halo sets up the foundation for RZKP but doesn’t actually implement the feature). @ebfull@therealyingtong
On the publicly facing side of this, from Chris Tomeo at Zcon:
Bouncing this thread with a request for any of you who are aware to add sub-link responses to deliverables in 2022 (are there any?) and any other items of interest that Zcash community has coming down the pipeline.
Related to the prior Zcash: Schedule snapshot - Did 5.3.0 deliver?
As far as I know the main objectives for the two next years are
New Wallet
Proof of Stake
Interoperability
2 and 3 are pretty connected, as they pretty much have a choice between either becoming a Cosmos zone or an Avalanche subnet.
My impression is that recursive ZKPs are not scheduled for the near future since they are prioritizing the PoS transition. Some of the smaller items JRGB mentioned will probably be done in parallel.
not trying to speak for any project, but… am i nuts … (well abstaining from the obvious)… but why isnt ycash the messaging layer considering particularly the spam issues with zec
id love to see some front facing reworking of the architecture that tries to compete with signal etc.
i mean, to give more color to my now 2 year long spiel about how ycash needs to be apart of the zcash funding system, does not anyone of you find it hilarious how we are reading “H1ghLy C0nf!d3n1aL” from elon and jack discussions via text messages?
It’s been a few weeks delayed as we’ve been simultaneously working on the mobile wallet SDKs while chasing down and fixing zcashd OOM issues. I think we’ve got the main zcashd problems fixed now (I just identified and fixed a significant performance issue that was affecting wallet scanning during -reindex), and we’re aiming to get a 5.3.0 release out later next week (assuming nothing else comes up).
@str4d Could you explain how or if recursive ZKP are going to help scability? I thought they would reduce verification time but trial decryption would still be necessarily for all actions.
Thanks HanH for bouncing that topic, I have been under the perception that part of the drive for Halo was that with a trustless setup, the protocol can now ben enhanced with notably less complexity (no more 300 person ceremonies needed). And that the Bounty #1 following would be the recursive zero knowledge proof solution. (@ebfull is that work still in R&D? I recall seeing that you’ve already got the solution)
