-
Use npm package directly https://github.com/hyperledger/aries-framework-go/packages/123279 instead of custom wasm build in the project.
-
- Add release notes
- Tag
-
The Signing and Verifier signature suite interfaces are not exported and they are part of APIs exported to the consumers.
1. Signing - The interface type for Suite field in LinkedDataProofContext …
-
RTC 267260
```
launchTck:junit.framework.AssertionFailedError: Timeout occurred. Please note the time in the report does not reflect the time until the timeout.
at jdk.internal.reflect.GeneratedM…
-
**Using MediatorAgent Service in aries-framework-dotnet/samples/routing/MediatorAgentService**
I started the MediatorAgent on http://localhost:5000 and provided this URI as endpoint for Osma Mobile …
-
currently we include `"credentialSchema": []` in our output but other implementation omit when empty.
-
-
After QR Scan on OSMA to make a connection with aries-framework-dotnet Web Agent, I get the following error.
**Error Log on OSMA**
```
Failed to send A2A message with an HTTP status code of Inter…
x0axz updated
4 years ago
-
We need the ability to verify that only context vocabulary is present in a VC, VP, LD Signature. i.e., how do we validate that a JSON-LD document only contains defined vocabulary?
Example Scenarios…
-