zupass future work ideation

[ichub]

short-term work (finishing up the year)

• import PCDs feature #1272
• turn off devconnect ticket re-issuance #1273
• frogcrypto tadpoles #1279
• fix sync #1271
• Generic rate limiting #1264

engineering level ups

• zupoll long-term strategy #1315
• re-evaluate all database models - do the tables make sense? #1313
• backend unit tests #1312
• evaluate better systems for the backend <-> database interface #1311
• split out zupass core from devconnect/zuconnect/zuzalu-specific code #1301
• evaluate whether and when to cleave the monolith #1295
• evaluate react state management frameworks #1291
• evaluate alternative client-server communication frameworks for zupass client and server #334
• advance the semaphore eddsa conversation #1282
• client-server integration tests #328
• client-side tests #327
• make CI faster #274
• make production build faster on render.com #273
• enable tsconfig - strict: true in passport client #642
• debugging in VS code of apps + tests #569
• linting - enable the best lints across the repo #553
• run prettier in CI  #533
• render blueprint for zupass instance #372
• fix duplicate deploy alert #349
• alerts for entire deploy process, from when it starts to when it ends #340
• better client-side logging, like on the server #335
• online-first sql IDE connected to dbs in render #1300
• JSON Canonicalization #829
• fix warnings in console #802

compat/solidity/performance

• evaluate redis for caching #1309
• evaluate more-performant database alternatives #1308
• enable horizontal scaling of zupass server #1307
• what is the e2ee sync end-game for zupass? #1298
• evaluate performant mobile-proving solutions #1294
• perform expensive client-side operations on a background thread #265
• lazy-load packages so that they only consume resources when they are used #307
• some older devices throw error for wasm - SecurityError: The operation is insecure #913
• zupass is slow to load #780
• PCD changes can be clobbered across multiple tabs #641
• ensure that when we deploy users get new code immediately after refreshing their page #589
• robust rolling deploys of the pcd/zupass backend #508
• check email delivery status #395
• JS bundle is large, takes significant time to parse and run #251
• WASM could not allocate memory error after >10 proofs are generated in a row #200
• check if user is in incognito mode and show error if so #71

product/ui:

• link multiple email addresses to a single 'account' #358
• in-passport PCD creation feature #346
• implement feature that lets users 'hide' some pcds #339
• plugin idea: use extism #264
• pcd search ui #325
• mobile apps #271
• browser extensions #270
• integrate with mud #268
• in-app screens should have inconsistent styling #755
• is this the best file explorer we can do? #765
• PCDs could have an 'info' button in their title bar which would open up a modal with more info #763
• make the file picker look more like a file picker #758
• 'main identity' card style/content #757
• friendlier ZK proving error messages #628

security

• evaluate security best-practices of identity management #1296
• ppl should not be able to download the salt of accounts they don't own #649
• where do we need to rate limit? #632
• data recovery (recovery key) #499
• 2fa? #1314
• evaluate security of allowing sites to set arbitrary nullifiers #192

devrel

• figure out some way of testing that packages work from outside the monorepo during CI #1036
• fix passport-interface import problem #965
• make sure packages are easy to install #421

protocol/sdk

• 3 levels of programmability #1297
• PCD metadata interface #187
• PCD metadata interface #187
• Find a way to better manage zk artifacts #648
• add “getMultiplePCD” API #773

zero knowledge

• merkle key-value store #1299
• integrate zkemail #113
• implement ZK ECDSA PCD #119
• collect performance metrics of zk proofs from mobile devices #365