OrgBook displays a Credential verified badge/link for credentials issued to a registered company that are current (not expired/replaced):
When following the link, a call to the /verify endpoint is performed: this triggers an internal proof-request that is used to validate the credential and generate the verification page (example: https://orgbook.gov.bc.ca/entity/FM0357337/credential/5785650).
With the imminent shutdown of Sovrin and the resulting move of BC Gov issuers from Sovrin to CANdy, all credentials issued on MainNet will become unverifiable as soon as the ledger the issuers were rooted on ceases to exist.
Updates to the UI are required in order to avoid user confusion when browsing records, and in particular:
Wording should be updated to reflect that the credential is not "verified", but may still be current
The self-verification step should be skipped, since it is not really providing added value (and it will not be possible for credentials issued on an retired ledger)
The verification page should still display the credential claims, but will not display the proof payload
Note: for credential types other than AnonCreds (such as W3C) the verify endpoint might be in use to extract the claims to be displayed in the UI. Functionality for this type of credentials must be retained.
OrgBook displays a
When following the link, a call to the
Credential verifiedbadge/link for credentials issued to a registered company that are current (not expired/replaced):/verifyendpoint is performed: this triggers an internal proof-request that is used to validate the credential and generate the verification page (example: https://orgbook.gov.bc.ca/entity/FM0357337/credential/5785650).With the imminent shutdown of Sovrin and the resulting move of BC Gov issuers from Sovrin to CANdy, all credentials issued on MainNet will become unverifiable as soon as the ledger the issuers were rooted on ceases to exist.
Updates to the UI are required in order to avoid user confusion when browsing records, and in particular:
Note: for credential types other than AnonCreds (such as W3C) the
verifyendpoint might be in use to extract the claims to be displayed in the UI. Functionality for this type of credentials must be retained.