-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix did:peer generator #50
Comments
Could not find a did:peer 2 generator that works, beyond the example of https://github.com/roots-id/didcomm-mediator There is no library we could use for this... Still troubleshooting what is wrong with the current implementation, error might be on keys generator? still on it. |
@hugoib and @forkimenjeckayang will sync to discuss the problem |
This is how we did it on the mediator: https://github.com/adorsys/didcomm-mediator-rs/blob/main/crates/web-plugins/did-endpoint/src/didgen.rs#L6 |
About my ticket, I’m still trying to match what is expected by the library vs what we are generating. My approach of the new secrets format is still failing I have one last idea to try. Since the error is inside the wasm rust library, it’s tricky to debug and the raised error might be on another place (?) |
For testing I am using an OOB inv from: https://mediator.rootsid.cloud which resolves to: Apparently there is an error there where according to the spec serviceEndpoint should have a URI field |
Needs proper adjustments and cleanups as seen here: feat/update-oob-contact-routing-explore |
Pending PR to close this here:
|
PR will be reviewed by @hugoib |
@IngridPuppet pls review |
The did peer generator is not generating properly the keys and keys IDs
The text was updated successfully, but these errors were encountered: