Application for Retroactive Funding for Pepper-Sync (second attempt)

@Edicksonjga put together this analysis of relative performance along with instructions for independent verification.

We’re looking into soliciting independent contributors to perform their own benchmarks, to replicate-or-contradict findings.

We see several significant performance enhancements, as documented below.

(Again this is @Edicksonjga 's work, and we’re interested in ironing out replication procedures to get independent observations.)

CAVEAT: We are also testing our new zainod offering (another dimension of variability..) and would be interested to see benchmark results against a zainod endpoint. Interested parties can reach out and we’ll furnish a zainod endpoint.

Pepper-Sync in the Zcash Ecosystem

I have tested on multiple platforms (iOS 26, Windows 11, and Arch Linux) using a wallet with a real transaction history and a block height of 2,900,000. The goal is to provide up-to-date data on the performance of Pepper-Sync on Zingo Mobile and Zingo PC.

Optimizing Fund Availability

One of Pepper-Sync’s core technical pillars is prioritizing user utility. Results demonstrate that users can transact long before the technical process of the full scan is complete.

User Metric Zingo Mobile/ZingoPC Result (Pepper-Sync)
Funds available to spend ~1:30 min
Total synchronization (100%) ~5:00 min
Spend Before Syncing Yes (Active and Functional)

Cross-Platform Stability

Tests conducted on desktop computers and mobile devices demonstrate fast application performance and synchronization, regardless of the operating system used. As you can see in the videos:

  • Zingo PC (Windows 11/Arch Linux): ~5 minutes for total synchronization and ~3 minutes for funds to be available via Spend Before Syncing.

Evolution and Technical Progress

In comparison to previous years and after sandblasting, where synchronizing a similar range of blocks could take between 20 and 60 minutes, the current Pepper-Sync implementation allows the process to be completed in 5 minutes, with funds available in as little as 90 seconds.

This improvement represents a qualitative leap in the usability of ZingoLabs applications, prioritizing immediate utility and the efficiency of the synchronization engine.

Test Data

  • Software: Zingo Mobile 2.0.18 (305) / Zingo PC 2.0.10.
  • Library: zingolib_v3.0.0-0-g8a663aa6.

Full audiovisual records of each test, supporting these times and the fluid performance of the interfaces, are available at the following link (Mega folder).

This folder contains videos of various Zcash wallets.

Another reference

ZingoLabs posted this video to celebrate the release of the first version of Pepper Sync:


How to run your own tests

  1. Install ZingoPC or Zingo Mobile.
  2. Restore your wallet or use our test wallet:

daughter safe tonight pull clarify discover gesture sting carry shine cup tourist say six ignore benefit wise argue issue above invest milk holiday source

  • To restore on ZingoPC: Click on Wallet and then Add new wallet.
  • To restore on Zingo Mobile: Open the menu and tap Restore or Open a new wallet.
  1. Add the birthday height: 2900000
  2. Tap on Restore.

What to expect

The synchronization process will begin. For this number of blocks, a full sync typically takes between 5 to 10 minutes. However, you should see spendable funds within 1:30 to 3 minutes.

Note: Performance results will vary depending on your device, the wallet version, the server, and your internet connection.

Pro-Tip

As an active user in the Zcash ecosystem, I recommend changing the global ZecRocks server to a different one. Because it is often saturated, you may experience occasional connection issues.

If you want to compare these results with another app, simply download and install it, then repeat these steps following the specific UI instructions of that application.

7 Likes

On my currnet PC (notebook), I was able to complete sync with this wallet using my private node (Raspi5) in 2:57 min, FYI

Also, I was able to “Spend funds” in 54.62 seconds at this point:

I hope more folks share their results, I’ve always thought we should have a public database with the same seeds that can be compared independently.

4 Likes

Can you confirm birthday/seed/version matching?

You are comparing apples to oranges. The sandblasting period had 100 X more data per block.

If you want to demonstrate how pepper sync handles the sandblasting, use a birth height during that period (1800000 for ex) instead of interpolating.

Yes, you are Zooko’s brother, which is not an issue in general, but does create a higher bar for you to clear socially. The appearance of nepotism can be harmful to both your application and the ecosystem, even if that is not the reality. The answer to that is a higher bar for transparency and results.

Given the various technologies listed on your application and the different types of grants received, I am actually confused about what you or your team have already gotten grants for already. The history of this org and it’s relationships is murky to me and anyone who was not involved, so I think your application would be improved by itemized disclosures of public funding, either directly or indirectly.

(fwiw this is just my opinion, have no idea what the rest of token voters think about this)

FYI, Using Zkool on this seed gives a sync time of 37 seconds total.

./dismad.sh  0.57s user 0.14s system 1% cpu 37.731 total

Script: Dropbox

Specs:
Model Name: MacBook Pro
Chip: Apple M4
Memory: 16 GB

2 Likes

You’ve misinterpreted it; I’m not comparing the current test to the sandblasting period, but to how synchronizing a similar range of blocks in Zingo was outside of the attack and before Pepper Sync.

1 Like

Yes, and this seems to be right