Zingo Labs produced pepper-sync (details in the proposal), we’re asking for retroactive funding for this Zcash enhancing, previously unpaid work.
Please see our proposal here!
I look forward to conversations with the community. I hope to get feedback from @peacemonger @hanh @NealJayu @decentralistdan @thowar2 and @outgoing.doze early on, as they have offered particularly useful criticisms in the past, and I very much appreciate their insights.
Thanks for your thoughtful attention!
Aye. Can’t promise that I will participate to that vote, but if I do that’s what I’ll do.
I am trying to use pepper-sync in zingo-cli.
when Re-org is detected, panic happens:
INFO pepper_sync::sync: Re-org detected.
thread ‘tokio-runtime-worker’ panicked at /usr/src/zingolib/pepper-sync/src/sync.rs:1284:10:
should be non-empty in this scope
I would love to use zingo-cli with pepper-sync as a server-side wallet, it fits my use cases very well, but these intermittent panics prevent me from deploying it in production.
I am willing to spend time helping diagnose and fix the issue. Would you be able to prioritize investigating this, or point me to the best place to coordinate on a fix? I have not had much success filing standard GitHub issues to report similar problems. Thank you
We’ll look into this right away!
There are 3 parts to this grant:
Pepper sync is only used by your own applications, ie, it is not part of any independent application. I actually don’t see why you didn’t choose an existing synchronization method and built your own, as it turns out to be slower. Is it for diversification?
No, ZingoLabs en Español (ZLE) has never received a grant from ZCG.
As mentioned here the ZExCavator work we were asking to be retroactively funded, which is subsequent to the ZeWIF covered work is in progress but not complete, and is therefore not eligible for retroactive funding.
I will edit the ask to remove the reference, and leave this message by way of explanation.
Our keysweeper work is in progress, and it was our intention to complete it in time for this retroactive funding application, but we reallocated our effort to support a Cross Link prototype mobile application first. The grant application should have been updated to track the shift in priorities and completed work.
Hi all I wanted to point out the @ZecHub is currently testing 
which uses Zingo’s Zingolib for the backend. We have been working with the Zingo devs and support has been amazing! Here is our open sourced code which we invite everyone to disect and find issues with – this platform is for the community so dont hold back 
We invite everyone to test with their testnet addresses and let us know about any issues/concerns/bugs! We recommend zingo, zkool, or zcash-devtool to generate testnet addresses!
Here is how they look:
this is great! I hope we can take this to production. It really solves a problem we’ve been having where there’s no incentivized on-ramp for contributors that helps teams to get contributions that are a priority for their roadmap which can’t be left to good will of pro-bono contributors but that aren’t substantial enough for a grant of their own.
The Zingo team developed a mobile wallet for our Crosslink testnet, which we’ve used in multiple workshops over the past several months. The wallet uses Pepper Sync and allows participants to interact with the network and see how things work in practice, including staking, unstaking, and redelegation.
They did a terrific job on the wallet’s design and user experience. It’s intuitive, easy to set up, syncs reliably, and works well in a workshop environment where people need to get up and running quickly. I’ve received positive feedback from attendees on the overall experience.
The team has been easy to collaborate with, and we value the work they’ve done to support our workshops.
Nice one. During Setup Required, all attempted zcash addresses kept failing with error Please enter a valid Zcash shielded address.
I’m not sure which setup you are referring to exactly but, given the context, it sounds like the wallet network was not configured properly i.e. its still on a mainnet server and/or account.
