feat: add driver for did:neuralkey method#571
Open
Neuralkey wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a new custom driver integration for the
did:neuralkeymethod to the Universal Resolver. The driver is built as a lightweight, standalone TypeScript/Express service and containerized using an optimized multi-stage production build.docker-compose.yml: Appended thedriver-did-neuralkeyservice and mapped the internal driver URL environment variable foruni-resolver-web.uni-resolver-web/src/main/resources/application.yml: Registered the regex pattern^(did:neuralkey:.*)$and added the appropriate test identifiers.README.md: Updated the driver capability matrix table to include theneuralkeymethod, specification link, and Docker Hub image repository.Docker Hub: The production-ready Docker image has been successfully built, tagged, and pushed to Docker Hub. It is publicly available for the Universal Resolver deployment.
Local Testing: I have successfully verified the entire integration locally on my Docker machine by running
docker compose up. The centraluni-resolver-webcore correctly identifies thedid:neuralkeypattern, routes the traffic to the custom driver container, and yields a valid DID Document response flawlessly.DID Method:
neuralkeyDocker Image: heanmengfong/neuralkey-did-driver:1.0.0