The @dcx-protocol monorepo should house the applicant, common and issuer logic agnostic to implementation. By this I mean, each should implement the respective side of the protocol, use common lib functions and have some basic handlers. The current implementation has lots of redundancies and env dependencies. This new package should contain the following:
DcxServer
Issuer needs a polling / server mechanism since its purpose is to run as a stateless credential exchange server. Applicant does not need the same mechanism since its purpose is to be used on the client side. We expect developers building applicant-side web apps to run a node server of some kind (next, etc).
bnonni
commented
3 weeks ago
The @dcx-protocol monorepo should house the applicant, common and issuer logic agnostic to implementation. By this I mean, each should implement the respective side of the protocol, use common lib functions and have some basic handlers. The current implementation has lots of redundancies and env dependencies. This new package should contain the following:
DcxServer
Issuer needs a polling / server mechanism since its purpose is to run as a stateless credential exchange server. Applicant does not need the same mechanism since its purpose is to be used on the client side. We expect developers building applicant-side web apps to run a node server of some kind (next, etc).
IssuerServertoDcxServerclassDcxServerinto server packageApplicantServer