Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DID Resolver #2

Open
brianorwhatever opened this issue Apr 3, 2024 · 1 comment
Open

DID Resolver #2

brianorwhatever opened this issue Apr 3, 2024 · 1 comment

Comments

@brianorwhatever
Copy link
Contributor

We can easily add an http resolver that would proxy to external DIDs. It gets a bit more challenging when we want to be resolving documents from the local filesystem. The biggest thing to think about is how do the files get to the filesystem.

I propose an upload endpoint that receives a log file and stores it to disk (only if the version is higher than currently saved and the log verifies).

@lemoustachiste
Copy link

Hi Brian,

so I'm wondering, it looks like at this time resolving documents from their hosted destination is the responsibility of the consumer, and that the resolver.ts file is for local/test only and that the method.resolveDid function is about verifying the validity of the resolved did log. Am I correct with this understanding? At this time, should I implement my own DID to HTTPS resolver?

Longer term, can we expect this package to handle file resolution from the DID?

Finally, is there a plan to port the resolver into the DIF universal resolver?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants