Merge pull request #105 from pacu/lcwg-82-83

This commit is contained in:
Pacu 2024-09-01 18:15:11 -03:00 committed by GitHub
commit 5169424604
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 100 additions and 2 deletions

View File

@ -29,13 +29,15 @@ Light client developers, Protocol developers, and lightwalletd developers are in
Generally every light client is represented. Sometimes a non-developer with particular expertise on a topic is invited on to discuss a specific agenda item. If you feel you would contribute to the meetings by your attendance please reach out to @pacu.
### Who Manages the Meetings
- @pacu as ZWCD takes notes and facilitates
- @decentralistdan facilitates and provides conference call venue on behalf of ZF
- @pacu as Zcash Dev Rel Engineer takes notes, facilitates and manages the conference call venue
- @decentralistdan from ECC facilitates.
### Previous Meetings
№ | Date | Agenda |Notes | Recording |
--- | -------------------------------- | -------------- |-------------- | -------------------- |
83| August 22nd, 2024 17:00 UTC | [agenda] | [notes](https://github.com/zcash/lcwg/blob/main/meeting-notes/lcwg-dev-83.md) | not recorded |
82| August 8th, 2024 17:00 UTC | [agenda] | [notes](https://github.com/zcash/lcwg/blob/main/meeting-notes/lcwg-dev-82.md) | not recorded |
81| July 25th, 2024 17:00 UTC | [agenda] | [notes](https://github.com/zcash/lcwg/blob/main/meeting-notes/lcwg-dev-81.md) | not recorded |
80| June 27th, 2024 17:00 UTC | [agenda] | [notes](https://github.com/zcash/lcwg/blob/main/meeting-notes/lcwg-dev-80.md) | not recorded |
79| June 13th, 2024 17:00 UTC | [agenda] | [notes](https://github.com/zcash/lcwg/blob/main/meeting-notes/lcwg-dev-79.md) | not recorded |

View File

@ -0,0 +1,64 @@
# Light Client Working Group Devs Meeting 82
### Meeting Date/Time: Thursday, August 8th, 2024 17:00 UTC
### Meeting Duration: 60 minutes
### Moderator: @pacu - ZWCD, @decentralistdan - ZF
### Attendees: Kris (ECC), Andrew (ezcash), Conrado (ZF), Pili (ZF), Za (Zingo), Fluid vanadium (Zingo), Za (Zingo)
## Agenda:
- Quick team updates
ZIP-320 integrated in librustzcash. But it requires additional changes on how transparent wallet history is handled because of how UTXOs are handled to implement autoshielding in the SDKs which is incompatible with how they should be handled to restore transparent transaction history. This entails updating ligthwalletd RPCs to walk the chain forward. (see requirements). See call to action for getrawtransaction issues.
- Decentralizing Core development:
- Lightwalletd and Zebrad RPC issues affecting wallets: fixes and deployment plans
- Implementing Zingo Indexer.
- Roadmap to mobile Hardware wallets:
- Brainstorm Requirements
- Partial Zcash transaction format
- Changes to transaction builders
- general purpose SDKs
- Orchard API and ZIP-312 implications for FROSTd wallets
- https://zips.z.cash/zip-0312
- https://github.com/pacu/frost-uniffi-sdk/pull/65
## decentralizing Core development
Someone needs to fix this https://github.com/zcash/lightwalletd/issues/493
ZF Zebrad team is adding this to the NU6 backlog https://github.com/ZcashFoundation/zebra/issues/8744
Zcashd wallet deprecation: Forward walk of the blockchain complete transparent Zcash support
Fluid Vanadium: Whats the standardized set of RPCs for lightclients that the zingo indexer needs to implement? According to Kris, the service.proto is the standard set of RPCs at the moment.
Whats needed to implement Zingo Indexer as a rust implementation more feature-rich replacement of lightwalletd?
Za: from a 30,000ft PoV im not sure what the set of requirements should be
Kris: there are two indexing components: one for Block Explorers and one for offloading scanning viewing keys to a service.
Link to the diagrams of the scanner: https://github.com/zcash/librustzcash/issues/1373#issuecomment-2076019340
Pacu: how can we gather all these requirements in one place to work them out?
## Roadmap to Hardware wallets
We couldnt discuss this because of lack of time.
## Orchard API and ZIP-312 implications for FROSTd wallets
- The missing bits of the ZIP is how to generate a FROST wallet, there are many ways to do it and it has to be discussed what is the best approach agree on it and put in in the ZIP.
Transaction plan format and randomizer handling
Has FROST been appointed as official threshold sig for NDFM?
No it hasnt there are questions around signature attribution and robustness of the protocol
According to Conrado attribution can be worked out by publishing verifying shares.
Zebrad indexer requirements:
ZI1: Index to walk the blockchain forward (through outpoints)
Zingo indexer requirements:
Required information to implement ZI1.
Make sure that the bugs specified in the issues linked below are not reproduced by it
## Calls to action
- Getrawtransaction issues
- https://github.com/zcash/lightwalletd/issues/493
- https://github.com/ZcashFoundation/zebra/issues/8744

View File

@ -0,0 +1,32 @@
# Light Client Working Group Devs Meeting 83
### Meeting Date/Time: Thursday, August 22nd, 2024 17:00 UTC
### Meeting Duration: 60 minutes
### Moderator: @pacu - ZWCD, @decentralistdan - ZF
### Attendees: Conrado (ZF), Kris, Eric & Willem (chainsafe), Fluidvanadium (Zingo), Andrea (ECC), Arya (ZF)
### Agenda
Team Updates
Problems with transactions being rejected and not getting to the “mempool” in Zebra 1.8.0
TEX Address support status
Follow up of previous calls to action
Getrawtransaction issues
https://github.com/zcash/lightwalletd/issues/493
https://github.com/ZcashFoundation/zebra/issues/8744
### Team Updates
Chainsafe:
starting to look at librustzcash wallet traits. They see a lot of influence between the sqlite and the backend.
Working on an In Memory wallet and branching off from Kris PR
### Zcashd deprecation
ChainSafe could actually take on the InMemory Wallet task https://github.com/zcash/librustzcash/issues/1414 if ECC developers agree that theres strategic value in them overseeing the development.
### problems with Zebra 1.8.0
Theres a branch fixing the problem on Zebra and a [lightwalletd issue being worked on by ECC](https://github.com/zcash/lightwalletd/issues/497)
### TEX address Status
Android and iOS SDK releases include TEX address support and EDGE and others should be able to upgrade to the latest version of the SDKs
https://github.com/Electric-Coin-Company/zcash-swift-wallet-sdk/releases/tag/2.2.1
[Android SDK deployment](https://github.com/Electric-Coin-Company/zcash-android-wallet-sdk/commit/a4550c24a598dd0088aef77ff17f6b0892e44418)