WarpSync aims to give you a fully synchronized wallet, with all your notes spendable as soon as possible. I think these methods are complementary and a wallet could offer the best algorithm based on the user choice.
Donât know where yâall guys from. But here in Africa , no batch-sync implementation fixed my lightwallet syncs (desktop and mobile) - an optimistic 4.0 Mbps.
Str4d please fix me oui
I would rather have more than 1 sync. Imagine if warp-sync and blaze-sync wouldnt exist? Zcash would already be dead. In a optimal world ECC should have competed with blaze sync and warp sync. Alas, they havnt. ECC havnt even benchmarked their sync vs other sync. It wasnt a priority.
Seems that ECC wont be implementing zcash/warp sync in librustzcash. Maybe the grant should change to reflect that. We can have a community funded sync that has so far outperformed the ECC devs sync.
The proposal is to add Warp-sync to librustzcash along with the existing synchronization. I didnât suggest replacing it. Wallet devs can choose what they prefer based on their target usage scenarios. Technically speaking, I donât see any reason why multiple sync implementations canât coexist in librustzcash.
@hanh & Zcash Community members, I am pleased to announce that the @ZcashGrants Committee has voted to approve the retroactive portion of the grant for $300,000 and the documentation milestone for $50,000 for a total of $350,000. Per your conversation with the committee, the wallet will remain a multi-currency wallet with the name âYWallet,â but a condition of the grant is for you to republish the wallet in the Apple App Store under your own account.
In addition, ZCG has decided to hold off voting on the librustzcash PR until they have more information from you, ECC, and other wallet developers. ZCG requests that you close out this portion of the grant and submit it as a new proposal.
Excellent, itâs great to see recognition for all of the great work that @hanh has been doing for the community and Zcash, looking forward to whatâs coming next.
This documentation starts with an overview of the purpose and architecture of Lightwallets. It describes the functionalities required by a synchronization library.
The next section describes the Data model. Warp Sync stores its data in a SQLite Database. Each major table is shown and its purpose explained.
Then, we show the synchronization workflow in the section Execution Model.
Feel free to skip ahead to the developer section if you just want to use it.
Developer Guide
We have several integrations.
The easiest is to run as a web service that provides synchronization and account management.
WarpSync can be used as a dynamic linked library from any language that supports FFI C bindings. For an example in JAVA, go to this section.
And finally, if you use rust, WarpSync is a crate that can be incorporated in your project. You will find an example here. The RustDoc is here.