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
Hi, we're currently making use of DRPC in one of our projects and are glad that the implementation within Credo-ts provides the basic framework for this protocol before we move to specifying our own.
However we've had to develop a few workarounds to manage message flows and verify signatures due to handling within recvRequest.
We'd like to be able to query previous message threads for responses, and respond to drpc requests via a function on the drpc module.
The AcaPy implementation seems to fulfil more of the RFC and so we'd like to make some changes to Credo-ts that are signposted there. Would we have your blessing to proceed and potentially commit back?
The text was updated successfully, but these errors were encountered:
I believe the repo is open to PRs so no blessing to be asked. Some members of the BC Gov team worked on the initial DPRC implementation in Credo-TS, so you might ping @wadeking98 when you have questions or want a review.
Hi, we're currently making use of DRPC in one of our projects and are glad that the implementation within Credo-ts provides the basic framework for this protocol before we move to specifying our own.
However we've had to develop a few workarounds to manage message flows and verify signatures due to handling within
recvRequest
.We'd like to be able to query previous message threads for responses, and respond to drpc requests via a function on the
drpc
module.The AcaPy implementation seems to fulfil more of the RFC and so we'd like to make some changes to Credo-ts that are signposted there. Would we have your blessing to proceed and potentially commit back?
The text was updated successfully, but these errors were encountered: