All ECC teams focused on wallet performance

thanks for an update, looking forward to it
:+1:

1 Like

Thanks for this!

I love that slogan: “protect the freedom, dignity, and consent of all people”.

2 Likes

My friend, please read this: do you believe I will be able to get my funds back on unstoppable wallet ? When ? That’s all I need to know. All other wallets are showing me a 0 balance. I cannot even check my wallet balance on chain, that’s an absurd.

Korean Zcash holders wanted a Zcash wallet made by ECC.

I’m looking forward to ZASHI :slight_smile:

6 Likes

put your seed into ywallet

4 Likes

Hey folks! Zooko the Engineering Manager here. Our team has been working super hard to hit our target (mentioned up-thread here) of shipping ECC Mobile Wallet SDK 2.0 Release Candidate today, and it is all code-complete and available in github right now! But we have hit a bunch of last minute issues in dependencies and build, indicating some weaknesses in our infrastructure and processes to manage that stuff. I’ve asked the team to get some sleep for once, and we’ll circle back to you Monday with an update.

(P.S. If you see any ECC engineers over the weekend give them a hug!! :laughing:)

24 Likes

Hello everyone! Zooko the ECC Engineering Manager reporting in.

I told you I’d update you on the ECC Mobile Wallet SDK 2.0 release on Monday (today). The status is that we’ve fixed the build/integration problems, discovered a bug (#963), fixed that bug, and we’re now doing a hopefully-final round of integration, code review, and testing. We currently expect to ship SDK 2.0 Release Candidate this Wednesday, the 13th. Here’s our updated SDK 2.0 release plan:

  • :ballot_box_with_check: #1179 and #1180 done (the last week of August).
  • :ballot_box_with_check: #730 and #899 #936 #908 completed
  • :ballot_box_with_check: Rest of the mobile code – code complete Friday 2023-09-08 excluding acceptance testing
  • :ballot_box_with_check: Fix bug (#963) discovered during acceptance testing
  • ☐ Code review of mobile code changes, release SDK 2.0 Release Candidate Wednesday 2023-09-13
  • ☐ Acceptance testing (potentially using Zashi beta) complete by Monday 2023-09-18. Release SDKs 2.0 Final! (* Assuming no bugs discovered in acceptance testing that require code changes.)
  • ☐ Ask for a thumbs up from Nighthawk, Edge, and Unstoppable that the release looks okay, make public announcement Friday 2023-09-22 if we get word from the wallet partners early enough or if not then public announcement on Monday 2023-09-25. (edited)
23 Likes

Hashtag monorepo

2 Likes

:hugs::open_hands::kissing_heart::kissing_closed_eyes::couplekiss_man_woman:

4 Likes

Ok folks! Zooko the Engineering Manager and Product Owner reporting in. I’m delighted to report that we’ve released ECC Mobile Zcash SDK 2.0 Release Candidate for iOS and Android!

For iOS: Release Zcash IOS SDK release 2.0.0-rc.1 · zcash/ZcashLightClientKit · GitHub

For Android, get zcash-android-wallet-sdk 2.0.0-rc1 from the sonatype Maven repository. (URL: Central Repository: cash/z/ecc/android/zcash-android-sdk/2.0.0-rc.1 )

This release implements Spend Before Sync! Meaning that users should be able to spend their ZEC without waiting for the syncing process to finish. Sync can now be, from the user’s perspective, a “background” process that they don’t need to care about.

This version has been tested internally by our team at ECC and has no known bugs that would have a high impact on users.

Here’s the remaining plan for the final release of SDK 2.0. We intend to make no changes from the 2.0-RC to 2.0-final except for bugfixes that are high impact and that seem sufficiently safe of a change to make.

  • :ballot_box_with_check: #1179 and #1180 done (the last week of August).
  • :ballot_box_with_check: #730 and #899 #936 #908 completed
  • :ballot_box_with_check: Rest of the mobile code – code complete Friday 2023-09-08 excluding acceptance testing
  • :ballot_box_with_check: Fix bug (#963) discovered during acceptance testing
  • :ballot_box_with_check: Code review of mobile code changes, release SDK 2.0 Release Candidate Wednesday 2023-09-13
  • ☐ Acceptance testing (potentially using Zashi beta) complete by Monday 2023-09-18. Release SDKs 2.0 Final! (* Assuming no bugs discovered in acceptance testing that require code changes that set back the schedule.)
  • ☐ Ask for a thumbs up from Nighthawk, Edge, and Unstoppable that the release looks okay, make public announcement Friday 2023-09-22 if we get word from the wallet partners early enough or if not then public announcement on Monday 2023-09-25.

Many thanks to my team at ECC for working long and hard to make this the best it can be! :smiling_face:

31 Likes

Spend Before Sync - a huge improvement, as a community member and community manager to onboarding new people will be amazing.

Thank you to the team.

12 Likes

Great, great news! :clap: :clap: :clap: :clap:

5 Likes

¡So good!. I don’t understand so much, but i know is a nice news… Congratulations…

4 Likes

Awesome to hear. A major step forward in zcash usability! We’ll get this upgrade on the roadmap for Edge.

17 Likes

:+1:t2: we are going to look into it shortly and try to integrate it​:pray:t2:

4 Likes

Hiya folks! The bad news is we’re not ready to ship ECC Mobile Wallet SDK 2.0 today, as we had hoped.

The good news is that the Nighthawk team has already begun testing and integrating it, and that plus our own internal testing (including using a hacked-up variant of the Zashi beta!) has turned up a few issues that we think are worth holding up the 2.0-final release so that wallets can rely on it instead of having to wait for a 2.0.1.

We currently expect to have all known issues triaged (i.e. either fixed or Known-Issue’ed) and SDK 2.0-final released this Wednesday, the 20th.

  • :ballot_box_with_check: #1179 and #1180 done (the last week of August).
  • :ballot_box_with_check: #730 and #899 #936 #908 completed
  • :ballot_box_with_check: Rest of the mobile code – code complete Friday 2023-09-08 excluding acceptance testing
  • :ballot_box_with_check: Fix bug (#963) discovered during acceptance testing
  • :ballot_box_with_check: Code review of mobile code changes, release SDK 2.0 Release Candidate Wednesday 2023-09-13
  • ☐ Acceptance testing complete by Monday 2023-09-20. Release SDKs 2.0 Final!
  • ☐ Ask Nighthawk, Edge, and Unstoppable to make announcements of their intentions: Friday 2023-09-22.

As always, please reach out to me with any questions or feedback! And as always, please give your friendly neighborhood ECC engineer an extra hug :hugs:

19 Likes

Are benchmark performance studies available for review?

Thanks

5 Likes

4 posts were split to a new topic: Engineers need hugs too!

Thanks for the update.

My feedback: More underpromising and overdelivering. At this point, I can’t trust any deadline being set for this project.

2 Likes

Hi, hanh! Thanks for the question. We’ve done only a little benchmarking and optimizing, just enough to meet requirement 2 from our four requirements to exit emergency mode:

  1. Users of Edge, Unstoppable, and Nighthawk can spend their current funds (funds that are already synced when they open their wallet).
  2. Users of those wallets can receive and become able to spend new incoming funds at a rate of a month’s worth of transactions in 1 hour.
  3. Users have confidence that the sync is making progress and will eventually complete.
  4. None of those wallets are impacted by frequent crashes or inconsistent behavior (such as failing to display some already synced transactions).

Beyond reaching that minimal performance threshold, we’re prioritizing Spend Before Sync (requirement 1) as well as requirements 3 and 4.

The idea is that it is good if users have to wait less because sync goes faster, but it is even better if users have to wait not at all because they don’t need it to sync before they can do their things.

That said, there are still cases where users do have to wait for sync — mainly the situation where your wallet has been closed for a long time (weeks/months/years), and you open it and then you’re waiting to see if anybody paid you while it was closed.

So if you or anybody wants to build comparable benchmarking for the sync speed of different codebases, I’d love to see the results. I believe there was some talk of doing this — maybe by Zingolabs? Maybe using darkside lightwalletd?

If anyone wants to dig into this, here’s our current code bases for Android and iOS:

5 Likes