DIDComm v2 fails to interoperate with another did:peer:2 system
Open
Nobody has claimed this yet.
bug
good first issue
help wanted
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 10
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
Have tried connection to demo.didcomm.org without success.
Note that one must use the branch proposed for issue #650 so that incoming DIDComm messages will even get parsed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the branch proposed for issue #650, then reproduce the connection attempt with demo.didcomm.org described in this issue. Trace why incoming DIDComm messages are not interoperable with the other did:peer:2 system, and verify that the connection and message exchange succeed against that system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100