-
Notifications
You must be signed in to change notification settings - Fork 13
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
Release 8 #192
Conversation
This file contains 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
…nto update-issuer-node-v2
added content for privado chain | fixed YT links
Universal links | Verifier changes
chore: add issuer node v2 docs
Unified addresses
Web Wallet & Mobile App Documentation
Issuer UI changes
minor fixes to issuer documentation
update links to onchain demos
Documentation for Privado Identity Chain
Minor Fixes to documentation
OBrezhniev
reviewed
Oct 23, 2024
- `credentialSchema`: URL pointing to the credential schema of type JSON. It could be a schema for `authclaim` or `coreclaim`. | ||
|
||
- `credentialStatus`: shows credentialStatus `id`, which is the Revocation status of the credential (presence or absence of the revocation nonce value), `revocationNonce` (zero or any value) and `type`(type of Proof, for example, SparseMerkleTreeProof). | ||
- `credentialSubject` _String_: identifier of the Subject for which credentials are to be retrieved. For example, did:polygonid:polygon:amoy:2qE1BZ7gcmEoP2KppvFPCZqyzyb5tK9T6Gec5HFANQ. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Old description of credentialSubject
was correct, this one - no. But looks like it's not the description problem, but incorrectly renamed param in this API call, it should have stayed subject
.
@demonsh please take a look.
minor fixes - release 8
OBrezhniev
approved these changes
Oct 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.