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
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).
The text was updated successfully, but these errors were encountered:
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?
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).
The text was updated successfully, but these errors were encountered: