This November, the Nighthawk team monitored increased usage of lightwalletd services and set plans to provision additional hardware and bandwidth to meet the increase in demand. We reported our plans and estimates to accommodate ZIP-317 fee mechanism changes on the Wallet Dev call. 1 received updates to handle additional transaction types. Shout out to @BostonZcash to report the issue!

Nighthawk Wallet updates:

Keep up with changes upcoming in the light client SDKs for Android and iOS.
Start searching for native app developers to work on Nighthawk Wallet 2.0 in 2023
App Changelog is published at 4
Light Client Working Group:

Attend bi-weekly LCWG calls to discuss upcoming mobile SDK changes and plans following NU5.
Merge the Wallet Dev call with the LCWG call for all wallet devs to share progress and blockers.
LCWG meeting briefs are available at GitHub GitHub – zcash/lcwg: Light Client Working Group project management repository 3 2

Goal: Keep up-to-date versions for zcashd & lightwalletd to continue providing high availability public infrastructure for light-wallet based Zcash applications.

lightwalletd servers saw an increase in bandwidth demands from 15Mbit/s to 35Mbit/s in November.
Maintain 100% uptime via load-balanced main-net and single instance test-net services
Continue maintaining the monthly warranty canary on 2 1

Goal: Provide a fast, lightweight, Tor-enabled, no-tracker/no-analytics/no-logging Zcash transaction explorer.

Added support to handle previously unknown transaction types: fix node warning for watcher · nighthawk-apps/zcash-explorer@64d4a1d · GitHub 2