Thanks for your persistent inquiry @thowar2 .
In regards to developer adoption:
The following parties (external to Zingo Labs) are publicly known to use pepper-sync :
-
https://zecfaucet.com (mainnet and testnet) via GitHub - james-katz/zingolib-wrapper
-
Telegram: Launch @ztip_bot via https://github.com/Carover0/ztip_public
-
NozyWallet
-
CrowdStore
Additionally we’ve signed a letter of intent to support MFKDF2 from @multifactor .
@dorianvp and @Juanky are core Zingo Labs contributors who have been integral to the development of pepper-sync and as mentioned by @aquietinvestor in the “Crosslink Workshop” post they are integrating it into the Crosslink Demo (including substantial UI design work).
Of course I am not at liberty to disclose other partnerships without partner consent, and couldn’t disclose the CrossLink Demo work until today for the same reason.
With regard to User adoption
I can’t speak to the specifics of the negative anecdotes you’re hearing, and am NOT claiming that unfinished work on the upcoming demo constitutes a claim on retroactive funding for pepper-sync.
Nevertheless your line of questioning requires me to assert that there’s active UI work in progress. Otherwise readers might be left with the incorrect belief that UX based on pepper-sync is fixed. This is not the case.
Finally, with regard to the utility of “fast sync”, this property is high has high variance. My guess is that your sample is biased to freshly-or-recently installed instances of Zashi, where indeed sync speed is less important.
About the utility to UX of sync speed
Sync speed is more important the older the funds are, this value increases non-linearly for wallets older than the “sandblast” because of the shape of transactions in that epoch. Therefore you may in fact have a biased sample with respect to the usefulness/useability permitted by faster sync.