You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on discussion today with @0xmad about PCD, we got those three points:
Forking the main PCD types from Zupass package, the advantage here is that we would be able to change the PCD structure according to our needs easily.
Installing only @pcd/pcd-types npm package developed from Zupass project, and start integrating it with our monorepo.
Adding types system similar to the PCDs for our current Verifiable Credentials and use it as our standard.
We would stick to option (2) as a solution of us now. And that would give us different advantages:
Easily introducing the PCD concept in events like DevConnect.
Clarifying that we are using and depending in the PCD concept defined by Zupass project so then we have a one unified concept for the same term.
For the third point we would need to have more discussions on that with the team. (Long-term discussion point for PCDs and VCs). ( @AtHeartEngineer@AndrewCLu )
We also discussed that we would start integrating those PCDs:
This issue for experimenting integrating PCDs inspired Zupass PCD project.
Tasks
The text was updated successfully, but these errors were encountered: