The Hyperbeckn is a decentralized infrastructure designed to transform how participants build trust and transact in a secure, scalable, and transparent environment. The goal is to embed trust into the flow of transactions.
To do so, it is essential to have a Credential object in the transaction flow. This Credential object must support various types of credentials and it needs to be included in various components used in transaction, like Agent, Customer, Organisation, Payment, Provider, Subscriber, Fulfillment, Item, Order etc.
Summary of the changes proposed
There already is a Credential schema defined in the protocol specification. As part of this PR the existing Credential Object was enhanced to support various type of credentials, including a Verifiable Credentials
Two new API endpoints ( cred/ and on_cred/) were added in the protocol specification to support fetching credentials.
Changes
Addition: Created schema/VC.yaml to represent a verifiable credential object.
Update: Changed schema/Credential.yaml to support Verifiable Credentials
Addition: Created schema/CredentialRequest.yaml schema to represent a credential request object.
Addition: created cred/ endpoint to be used to request a credential from an entity
Addition: created on_cred/ endpoint to be used as callback to provide the requested credentials.
Addition: Added a boolean verified field in the context schema
Description
The Hyperbeckn is a decentralized infrastructure designed to transform how participants build trust and transact in a secure, scalable, and transparent environment. The goal is to embed trust into the flow of transactions.
To do so, it is essential to have a Credential object in the transaction flow. This Credential object must support various types of credentials and it needs to be included in various components used in transaction, like Agent, Customer, Organisation, Payment, Provider, Subscriber, Fulfillment, Item, Order etc.
Summary of the changes proposed
There already is a Credential schema defined in the protocol specification. As part of this PR the existing Credential Object was enhanced to support various type of credentials, including a Verifiable Credentials
Two new API endpoints ( cred/ and on_cred/) were added in the protocol specification to support fetching credentials.
Changes
schema/VC.yamlto represent a verifiable credential object.schema/Credential.yamlto support Verifiable Credentialsschema/CredentialRequest.yamlschema to represent a credential request object.cred/endpoint to be used to request a credential from an entityon_cred/endpoint to be used as callback to provide the requested credentials.verifiedfield in the context schema